Any MCP Client

Any application that supports the Model Context Protocol can connect to Toolcog. This guide covers the fundamentals for clients not specifically documented elsewhere.

Prerequisites

• An MCP-compatible client application
• A Toolcog account (sign up)

What You Need to Know

The Server URL

Toolcog’s MCP server is available at:

https://mcp.toolcog.com

For custom catalogs, append the owner and catalog name:

https://mcp.toolcog.com/{owner}/{catalog}

Transport Type

Toolcog uses Streamable HTTP transport (the MCP standard for remote servers). Your client must support HTTP-based MCP connections, not just local stdio processes.

When configuring your client:

• Transport type: HTTP, SSE, or “remote” (terminology varies by client)
• URL: https://mcp.toolcog.com
• No command or args: This isn’t a local process—just a URL

Authentication

Toolcog uses OAuth 2.1 for authentication. When you first use a tool that requires your Toolcog account:

1. The server returns an authorization URL
2. Your client should display this URL or open it automatically
3. Sign in to Toolcog in your browser
4. Return to your client—authentication is complete

This same pattern applies when accessing downstream services (GitHub, Stripe, etc.) through Toolcog.

Configuration Patterns

Different clients use different configuration formats. Here are the common patterns:

JSON Configuration

Most clients use a JSON file:

{
  "mcpServers": {
    "toolcog": {
      "url": "https://mcp.toolcog.com"
    }
  }
}

Some clients use a different structure:

{
  "servers": {
    "toolcog": {
      "type": "http",
      "url": "https://mcp.toolcog.com"
    }
  }
}

YAML Configuration

Some clients prefer YAML:

mcpServers:
  toolcog:
    url: https://mcp.toolcog.com

Environment-Based

Some clients accept server URLs via environment variables or command-line arguments. Check your client’s documentation for the specific mechanism.

The Three Tools

Once connected, your client gains access to three API meta-tools:

These three tools unlock access to 100,000+ API operations. Your AI uses them to discover, learn, and execute any operation dynamically.

Verifying the Connection

Ask your AI assistant:

“What GitHub operations are available for creating issues?”

If it returns a list of operations with descriptions, Toolcog is connected and working.

Troubleshooting

Connection Refused

• Verify the URL is exactly https://mcp.toolcog.com
• Ensure your client supports HTTP/remote MCP servers
• Check that HTTPS is not being blocked by a firewall or proxy

Tools Not Appearing

• Some clients require a restart after adding servers
• Check that the server is enabled in your client’s settings
• Verify the configuration file syntax is valid

Authentication Failures

• Click the authorization link when prompted
• Ensure you’re signed in at toolcog.com
• Try disconnecting and reconnecting the server

”Unsupported Transport” Errors

Your client may only support local (stdio) MCP servers. Toolcog requires HTTP transport support. Check your client’s documentation to confirm remote server support.

Client Requirements

For full compatibility, your MCP client should support:

• HTTP transport: Required for connecting to remote servers
• OAuth 2.1: Required for authentication flows
• Tool streaming: Recommended for responsive tool execution

Most modern MCP clients support these features. If your client lacks HTTP transport support, check for updates or consider using a client from our documented list.

Building Custom Clients

If you’re building an MCP client or integrating MCP into an application, see our SDK guides:

• Anthropic SDK
• OpenAI SDK
• Vercel AI SDK
• LangChain
• LlamaIndex

Next Steps

• Quick Start — Your first API operation
• API Meta-Tools — How discovery, learning, and execution work