MCP
Remote MCP connection to the public TeamPanel API for AI clients such as Cursor.
MCP
AI clients such as Cursor can use the public TeamPanel API via Remote MCP — with the same team API key as for regular HTTP requests.
Endpoint
https://api.team-panel.com/mcpTransport: Streamable HTTP, stateless (no sticky MCP session). Rate limits match the HTTP API: 32 requests / 10 seconds per key.
Same key
Auth is identical to the public HTTP API: Authorization: Bearer TP_…. Create keys under
Administration → API Keys (Superadmin). See API Keys.
Cursor
In your MCP config (e.g. .cursor/mcp.json):
{
"mcpServers": {
"teampanel": {
"url": "https://api.team-panel.com/mcp",
"headers": {
"Authorization": "Bearer TP_your_key"
}
}
}
}Replace TP_your_key with your team API key.
Tools
All tools are scoped to the key’s team and the permissions of the linked member (otherwise the team owner).
| Tool | Purpose |
|---|---|
get_context | Team ID, acting member, API key metadata |
search_api | Search the public OpenAPI by keyword or tag |
get_endpoint | Schema for an HTTP method + path |
call_api | Execute a public /v1/… request |
Typical flow: start with get_context (team ID), then search_api or get_endpoint, then call_api.
You may use {teamId} in paths — the endpoint replaces it with the key’s team.
Integrator routes only
call_api only allows routes from the public spec
(/openapi.json). Internal, admin, auth, and API key
CRUD routes are not available. What remains blocked with API keys is listed under
Authentication.