Before you begin
- API key – Create one at useagents.site/dashboard → Settings → API Keys. Keys are organization-scoped (WorkOS).
- MCP support – Your agent must support the Model Context Protocol (MCP).
Connection details
| Setting | Value |
|---|---|
| URL | https://mcp.useagents.site/mcp |
| Auth | API key in the x-api-key header |
Add the server to your agent
Add the UseAgents MCP server to your agent’s config. Pass your API key in the headers.Cursor
In Cursor settings (or.cursor/mcp.json), add:
USEAGENTS_API_KEY with the API key from your dashboard.
Claude Desktop
In your Claude Desktop config (e.g.~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
Windsurf
Add the samemcpServers block to your Windsurf MCP configuration with the UseAgents URL and x-api-key header.
Generic MCP config
Any MCP client that supports HTTP transport and custom headers can use:Verify the connection
After saving the config and restarting your client:- Open your MCP-compatible agent.
- Confirm the
useagentsserver appears in the MCP server list, if your client shows one. - Ask the agent to search for a tool such as “find a TypeScript SDK for Stripe webhooks” using
search_tools. - Confirm the response includes structured tool results rather than a connection error.
Troubleshooting
- Authentication failed: Verify the
x-api-keyheader is present and the key belongs to the correct organization. - Server does not appear: Restart the MCP client after editing the config file.
- Requests fail unexpectedly: Re-copy the URL exactly as
https://mcp.useagents.site/mcpand remove extra whitespace or trailing characters.
Get an API key
- Go to useagents.site and sign in.
- Create or select an organization.
- Open Settings → API Keys.
- Create a new API key and copy it immediately. You will not be able to see it again.
API keys are organization-scoped. Use the same key for all tools in that
organization.
Next steps
- MCP Tools Reference to learn what the server exposes
- API Keys for credential management and security guidance