Configuration Details

Got an AI assistant that's not in our main setup grid? No worries! Here's how to connect any MCP-compatible client to our Bitly server.

Authentication Methods

The Bitly MCP Server supports two authentication methods:

OAuth 2.1 (Recommended)

For clients that support OAuth with Dynamic Client Registration:

• Authorization URL: https://bitly.com/oauth/authorize
• Token URL: https://api-ssl.bitly.com/v4/oauth/access_token
• Scope: mcp.all

Your OAuth-compatible client will handle the authentication flow automatically, including:

• Dynamic client registration
• Authorization and token exchange
• Token refresh

API Token (Alternative)

For simpler setups or clients without OAuth support, use your Bitly API token from bitly.com/settings/api.

Universal HTTP Configuration

For any AI assistant that supports HTTP transport with API token authentication, use this pattern:

{
  "mcpServers": {
    "Bitly": {
      "type": "http",
      "url": "https://api-ssl.bitly.com/v4/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BITLY_AUTH_TOKEN"
      }
    }
  }
}

Just swap out YOUR_BITLY_AUTH_TOKEN with your actual token from bitly.com/settings/api.

For OAuth-compatible clients, refer to your client's OAuth configuration documentation and use the Bitly OAuth endpoints listed above.

Platform-Specific Configs

Continue

Add to your Continue config:
json

{
  "mcpServers": {
    "Bitly": {
      "type": "http",
      "url": "https://api-ssl.bitly.com/v4/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BITLY_AUTH_TOKEN"
      }
    }
  }
}

Remember to swap out YOUR_BITLY_AUTH_TOKEN with your actual token from bitly.com/settings/api.

Cline

Similar HTTP setup works for Cline and most other MCP clients.

For Stdio-Only Clients

Some clients only support local stdio connections. You can proxy our remote server locally using NPX:
json

{
  "mcpServers": {
    "Bitly": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api-ssl.bitly.com/v4/mcp",
        "--header",
        "Authorization: Bearer ${AUTH_TOKEN}"
      ],
      "env": {
        "AUTH_TOKEN": "YOUR_BITLY_AUTH_TOKEN"
      }
    }
  }
}

This uses the handy mcp-remote package to bridge HTTP to stdio.

Remember to swap out YOUR_BITLY_AUTH_TOKEN with your actual token from bitly.com/settings/api.

Verify Your Connection

Once you've added the config, restart your AI assistant and try:

"What Bitly tools are available?"

You should see a list of all our available functions. If not, double-check:

1. Your API token is correct and active
2. The config syntax is valid JSON
3. You've restarted your client after making changes
4. Your client supports the transport type you're using

Troubleshooting Config Issues

Config file not found?

• Make sure you're editing the right file for your platform
• Some tools need the config directory created first

JSON syntax errors?

• Use a JSON validator to check your config
• Watch out for trailing commas in JSON

Tool not connecting?

• Verify your API token hasn't expired
• Check that your client supports HTTP transport or stdio with npx