Documentation Index
Fetch the complete documentation index at: https://docs.swoop.it/llms.txt
Use this file to discover all available pages before exploring further.
Any client that supports the Model Context Protocol can connect to Swoop. This guide covers the general setup for clients not listed in the dedicated guides.
Prerequisites
- A Swoop account at swoop.it
- An MCP-compatible client that supports Streamable HTTP transport
Endpoint
Point your client to the Swoop MCP server:
Connection methods
Direct connection
Using mcp-remote
API key
If your client supports Streamable HTTP with OAuth natively:Add a new MCP server
In your client’s MCP configuration, add a new server with the endpoint URL above.
Authenticate
Your client will initiate an OAuth flow. Sign in with your Swoop account and approve the consent screen.
Verify
Confirm that ask_swoopAgent appears in the list of available tools.
If your client only supports stdio-based MCP servers, use mcp-remote as a bridge:{
"mcpServers": {
"swoop": {
"command": "npx",
"args": [
"mcp-remote@latest",
"https://swoop.it/api/mcp"
]
}
}
}
For clients that don’t support OAuth, authenticate with an API key by including it as a Bearer token in each request:Authorization: Bearer ak_your_api_key_here
mcp-remote, pass the key via the --header flag:{
"mcpServers": {
"swoop": {
"command": "npx",
"args": [
"mcp-remote@latest",
"https://swoop.it/api/mcp",
"--header",
"Authorization:Bearer ak_your_api_key_here"
]
}
}
}
Tested clients
The following clients have been verified to work with the Swoop MCP server:
| Client | Transport | Auth |
|---|
| Claude Desktop | stdio via mcp-remote | OAuth |
| Claude Web & Mobile | Streamable HTTP | OAuth |
If your client isn’t listed above, it should still work as long as it supports MCP over Streamable HTTP (directly or via mcp-remote). If you run into issues, check Troubleshooting. 
