Client Setup

Every client connects to the same hosted endpoint and authenticates through the same browser OAuth flow. Only the place you paste the URL changes.

MCP server URL

https://mcp.blockworks.com/mcp

Add Blockworks as a custom connector in Claude on the web or in the desktop app.

Open connector settings

Go to claude.ai/settings/connectors.

Add a custom connector

Click Add custom connector.

Enter the server URL

Use https://mcp.blockworks.com/mcp.

Connect and authenticate

Click Connect, then enter your Blockworks API key when the OAuth window prompts you.

Blockworks then appears in the connectors list for your chats. Enable it in a conversation to let Claude call its tools.

Add the server with one command:

claude mcp add --transport http blockworks https://mcp.blockworks.com/mcp

By default this registers the server for your user across projects. Add --scope project to write it into the project’s .mcp.json so your teammates pick it up too.Equivalent JSON, if you prefer to edit the config directly:

.mcp.json

{
  "mcpServers": {
    "blockworks": {
      "type": "http",
      "url": "https://mcp.blockworks.com/mcp"
    }
  }
}

Then, inside Claude Code:

Run /mcp to see the server and start the browser OAuth flow if it has not run yet.
Confirm the server shows as connected and its tools are listed.

claude mcp list shows every configured server and its connection state, which is useful for confirming the entry landed in the scope you expected.

Claude Desktop connects to hosted servers through the same custom connector mechanism as claude.ai.

Open settings

In Claude Desktop, open Settings and go to Connectors.

Add a custom connector

Click Add custom connector and enter https://mcp.blockworks.com/mcp.

Authenticate

Click Connect and enter your Blockworks API key in the browser window that opens.

Custom connectors are the supported path for remote servers. The claude_desktop_config.json file is for local stdio servers and is not the right place for a hosted HTTP endpoint.

Add Blockworks to your Cursor MCP configuration: ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside a single project:

.cursor/mcp.json

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

Reload Cursor, open Settings and then MCP, and confirm the server is listed. Click through the OAuth prompt and enter your Blockworks API key when asked.

ChatGPT reaches remote MCP servers through developer-mode connectors.

Open connector settings

Go to chatgpt.com/admin/ca#available.

Enable developer mode

Turn on developer mode so custom connectors can be created.

Create the connector

Click Create.

Enter the server URL

Use https://mcp.blockworks.com/mcp.

Leave authentication as OAuth

Do not switch to another authentication type, because the server uses OAuth.

Create and authenticate

Click Create, then enter your Blockworks API key when prompted.

Developer-mode connectors may be restricted by your workspace administrator. If the option is missing, ask your ChatGPT workspace admin to enable it.

Any MCP client that supports remote servers can connect with:

URL: https://mcp.blockworks.com/mcp
Transport: HTTP
Authentication: OAuth 2.0, handled by the client

Most clients use the same config shape:

{
  "mcpServers": {
    "blockworks": {
      "type": "http",
      "url": "https://mcp.blockworks.com/mcp"
    }
  }
}

Some clients omit type and infer the transport from the URL. If yours rejects the field, drop it and keep url.

Clients that only support local stdio servers cannot connect to a hosted URL directly. You need a client with remote server and OAuth 2.0 support.

Verify the connection

Whichever client you used, confirm the tools actually loaded before you rely on an answer:

What Blockworks tools do you have available?

If the assistant lists Blockworks tools, you are connected. If it lists none, or answers from general knowledge instead of calling a tool, work through Troubleshooting.

Getting Started

Guides

Tools Reference

MCP server URL

Verify the connection

MCP server URL

​Verify the connection

Verify the connection