Connecting AI Tools
This guide covers connecting MCP-compatible AI tools — including Codex, Cursor, Windsurf, and Claude — to your Telebugs instance.
Codex
- Open Settings → MCP servers in the ChatGPT desktop app.
- Select Add server.
- Enter a name, choose Streamable HTTP, and use your Telebugs URL:
https://your-telebugs-instance.com/mcp
- Save the server and restart the app.
- Select Authenticate, sign in to Telebugs, and approve the requested scopes.
Type /mcp in the composer to verify that Telebugs is connected. The desktop
app, Codex CLI, and Codex IDE extension share MCP configuration on the same
Codex host.
To configure Codex directly, add the server to ~/.codex/config.toml:
[mcp_servers.telebugs]
url = "https://your-telebugs-instance.com/mcp"
Then run codex mcp login telebugs to authorize the connection. Use
codex mcp list or /mcp to verify it.
See the Codex MCP documentation for additional configuration options.
Cursor
- Open Cursor Settings → MCP.
- Add a new MCP server with your Telebugs URL:
{
"mcpServers": {
"telebugs": {
"url": "https://your-telebugs-instance.com/mcp"
}
}
}
- Cursor discovers OAuth metadata automatically and prompts you to sign in.
- Approve the requested scopes on the Telebugs consent screen.
- Once connected, Telebugs tools appear in Cursor’s tool list.
To revoke access later, go to Account Settings → Connected apps in Telebugs.
Windsurf
Windsurf follows the same OAuth discovery flow. Add your Telebugs MCP endpoint in Windsurf’s MCP server configuration:
{
"mcpServers": {
"telebugs": {
"url": "https://your-telebugs-instance.com/mcp"
}
}
}
Sign in when prompted and approve the connection.
Claude
Claude connects to Telebugs as a remote MCP custom connector. This works in Claude on the web, Claude Desktop, and Cowork.
Note: Unlike Cursor and Windsurf, Claude does not call your Telebugs instance from your computer. Connections originate from Anthropic’s infrastructure, so your Telebugs instance must be reachable over the public internet. Private networks, VPN-only hosts, and
localhostwill not work.
Pro and Max plans
- Open Customize → Connectors in Claude.
- Click +, then Add custom connector.
- Enter your Telebugs MCP URL:
https://your-telebugs-instance.com/mcp
- Click Add, then Connect when prompted.
- Sign in to Telebugs and approve the requested scopes on the consent screen.
Team and Enterprise plans
An Owner must add the connector first under Organization settings → Connectors. Choose Custom → Web and enter the same MCP URL. Team members then connect individually from Customize → Connectors.
Using Telebugs in a conversation
Enable the Telebugs connector for a chat via the + button → Connectors. Claude discovers OAuth metadata automatically — no manual client registration is required on your side.
To revoke access, disconnect the connector in Claude or remove the app under Account Settings → Connected apps in Telebugs.
Other MCP Clients
Any MCP client supporting Streamable HTTP transport and OAuth 2.0 discovery can connect to Telebugs. The server advertises:
- Transport:
streamable-http - Protocol version:
2025-06-18 - Discovery:
/.well-known/mcp.json
Supported redirect URI schemes for OAuth include https://, http://localhost,
and custom schemes (cursor://, windsurf://, vscode://).
API Key Setup (Manual / Scripting)
If your client supports Bearer token authentication but not OAuth, use your REST API key:
- Copy your API key from Account Settings → API access.
- Configure the client to send
Authorization: Bearer tlbgs_...on MCP requests.
See Authentication for details.
Verifying the Connection
After connecting, ask your AI tool to list your Telebugs projects. It should call
list_projects_tool and return your accessible projects with stats. To assign
errors, it can call list_project_users_tool to discover team member IDs.
For an end-to-end investigation check, open an error in Telebugs, select Copy
for LLMs, and paste the prompt into the connected coding agent. Its first
Telebugs call should be get_investigation_context_tool.
If authentication fails, check:
- The Telebugs URL is correct and reachable
- Your account is active
- The connected app has not been revoked under Connected apps