Add Parceled to your agent
in under a minute
Copy-paste configs for every major MCP client. OAuth flow kicks in automatically on the first tool call: no API key setup required.
https://www.parceled.ai/api/mcpstreamable-httpOAuth 2.1 · DCRClaude (web, desktop, mobile)
in-app setupAdd as a custom connector: native Streamable HTTP + browser OAuth. No bridge, no local subprocess, no config file.
Customize → Connectors → Add custom connector
URL: https://www.parceled.ai/api/mcp
Claude opens a browser for the sign-in, returns on success, and
exposes all Parceled tools in the chat. On Team and Enterprise plans
an owner adds the connector once under Organization settings.The connection follows your Claude account to the desktop and mobile apps and syncs into Claude Code. Disconnect any time from the same Connectors screen.
Claude Code
commandNative Streamable HTTP MCP. One command.
claude mcp add --transport http parceled https://www.parceled.ai/api/mcpClaude Code walks you through the OAuth flow on the first tool call. No API key needed if you OAuth.
ChatGPT
in-app setupAdd Parceled as a custom MCP server (developer mode). Works on the web; the connection then follows your account.
chatgpt.com/plugins → + → Add custom MCP server
Name: Parceled
URL: https://www.parceled.ai/api/mcp
Auth: OAuth → Scan tools
Sign in with your email and the 6-digit code when prompted.Custom MCP servers need ChatGPT developer mode: turn it on in settings first. On Business and Enterprise workspaces an admin enables it.
OpenAI Codex
commandCodex CLI, IDE extension and the Codex desktop tab read the same config.
codex mcp add parceled --url https://www.parceled.ai/api/mcp
codex mcp login parceled
# or in ~/.codex/config.toml
[mcp_servers.parceled]
url = "https://www.parceled.ai/api/mcp"codex mcp login opens a browser for the OAuth sign-in and stores the token locally. Codex cloud tasks only see installed plugins, not local config.
Cursor
configNative Streamable HTTP. Dynamic Client Registration + browser OAuth handled automatically.
~/.cursor/mcp.json{
"mcpServers": {
"parceled": {
"url": "https://www.parceled.ai/api/mcp"
}
}
}Cursor supports static OAuth client credentials as an override, but Parceled advertises DCR via /.well-known/oauth-authorization-server so the default flow just works.
Zed
configAdd a remote context server in Zed settings.json. Omit the Authorization header and Zed will auto-prompt for OAuth on first call.
~/.config/zed/settings.json{
"context_servers": {
"parceled": {
"url": "https://www.parceled.ai/api/mcp"
}
}
}Zed distinguishes remote vs stdio servers by the presence of `url` vs `command`. When no `Authorization` header is configured, Zed runs the standard MCP OAuth flow in a browser on first connect.
Cline (VS Code)
configNative Streamable HTTP in cline_mcp_settings.json. OAuth auto-handled.
~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json{
"mcpServers": {
"parceled": {
"type": "streamableHttp",
"url": "https://www.parceled.ai/api/mcp"
}
}
}Cline auto-creates an OAuth provider for any streamableHttp or sse server; no Bearer token needed up front. First tool call triggers the browser flow.
Any other MCP client
configPoint at the Streamable HTTP endpoint. Dynamic Client Registration + PKCE is supported end-to-end.
Endpoint: https://www.parceled.ai/api/mcp
Transport: streamable-http
Protocol: MCP 2025-11-25
Auth: OAuth 2.1 (DCR per RFC 7591): or Bearer <api_key>
Discovery: https://www.parceled.ai/.well-known/oauth-protected-resource
Manifest: https://www.parceled.ai/.well-known/mcp.jsonIf your client is stdio-only and has no remote/HTTP option, the community mcp-remote npm package (github.com/geelen/mcp-remote) bridges stdio to Streamable HTTP. Not required for any of the clients above.
Not using MCP?
The same data is available via GraphQL or REST: use whichever fits your stack.
POST https://www.parceled.ai/apiApollo sandbox at /api. Same field-level billing.
GET https://www.parceled.ai/api/v1/parcelsOpenAPI 3.1 spec: /.well-known/openapi.yaml. Ready for OpenAI GPT Actions, LangChain, Zapier.
FAQ
Discovery surface
Everything a machine needs to find and integrate Parceled.
- /llms.txt : short agent pitch + endpoint map
- /llms-full.txt : full reference: tools, auth, error modes
- /.well-known/mcp.json : MCP discovery manifest
- /.well-known/openapi.yaml : OpenAPI 3.1 spec for REST surface
- /.well-known/oauth-protected-resource : RFC 9728
- /.well-known/oauth-authorization-server : RFC 8414