Connect your AI

Setup by app

Steps for each AI app that can use the iKnow Blockchain connection, with install links where the app offers them. Every app uses the same address and the same free sign-in.

Connection address

https://mcp.iknowblockchain.com/mcp

Read-only. No payment, wallet, seed phrase or private key is ever needed.

What you still type

An install link fills in the name and the address; you confirm in the app and sign in. Without a link, you type the name, or paste the address and the settings shown for your app.

No app documents taking a name, description or icon from the connection when you add it, so what you type is what the app shows.

Tested on this address

Claude

Owner sign-in and real tool calls passed on this address, checked Oct 13, 2026.

Add to Claude (external site)

Opens Claude on the web with the Add custom connector dialog already showing the name iKnow Blockchain and the connection address. Check both, choose Add, then sign in when asked.

Step-by-step instructions, including the sign-in choices: Claude on the Connect page.

ChatGPT

Owner sign-in and real tool calls passed on this address in ChatGPT on the web, checked Oct 13, 2026.

ChatGPT has no install link. Steps: ChatGPT on the Connect page.

These tests used the sign-in through Auth0, before October 18, 2026. Through our own sign-in page, Claude and ChatGPT signed in with Google and answered on our staging service on Oct 14, 2026.

Set up, not yet tested

Our sign-in service reads these apps’ own published identities, so there is no client ID to enter. No sign-in through it has been recorded on this address for them yet. If one fails, email [email protected] with the app’s name and version.

Claude Code

In a terminal, run:
claude mcp add --transport http iknow-blockchain https://mcp.iknowblockchain.com/mcp
To use it in every project, add --scope user after add.
In Claude Code, type /mcp, select iknow-blockchain and follow the sign-in prompt in your browser.
Run the connection check.

App documentation: Claude Code: MCP (external site)

Codex (CLI, IDE extension and ChatGPT desktop app)

In a terminal, run:
codex mcp add iknow-blockchain --url https://mcp.iknowblockchain.com/mcp
Or add it to ~/.codex/config.toml:
```
[mcp_servers.iknow-blockchain]
url = "https://mcp.iknowblockchain.com/mcp"
```
Run codex mcp login iknow-blockchain and sign in in your browser.
The Codex IDE extension and the ChatGPT desktop app use the same settings. Run the connection check.

App documentation: Codex: Model Context Protocol (external site)

Grok

Works from October 18, 2026, when this address moves to our own sign-in. Before then, Grok cannot sign in to it. Not yet tested on this address. On our staging service, Grok signed in through our sign-in page with Google and answered in an owner test, checked Oct 14, 2026.

In Grok on the web, open grok.com/connectors (external site) and choose New Connector, then Custom.
Name it iKnow Blockchain and paste the connection address. There is no client ID to enter: Grok identifies itself to our sign-in service with its own published details.
Sign in when Grok opens our sign-in page: choose Continue to sign in, then Continue with Google.
In a chat, check that iKnow Blockchain is turned on in the Connectors menu, then run the connection check.

xAI says connectors are available to all Grok users, and that on Grok Business and Enterprise a team admin sets a connector up first. Menu names can change between Grok versions. To disconnect later, remove the iKnow Blockchain connector in Grok.

App documentation: xAI: Grok connectors (external site)

Apps that use the iKnow Blockchain client ID

These apps sign in with one shared client ID, which you enter in their settings; the install links fill it in. It is public, has no secret and grants read access only after you sign in.

ikb.public

Apps that share a return address. Each app that uses this client ID keeps its own connection, except apps that use the same sign-in return address, such as Gemini CLI, Qwen Code and Kiro, or Cline, Kilo Code and OpenCode. On your own computer, a different port does not make a different return address. With the same Google or reviewer account, signing in from one of those apps ends the other’s connection within 15 minutes. Signing in again from the same app, even on another computer, normally replaces its earlier connection. A sign-in from one of these apps never ends the connection of an app with its own published details, such as Claude, ChatGPT or Grok.

New ID from October 18, 2026. This ID belongs to our own sign-in service. The earlier ID, which starts with tpc_, worked only with the sign-in through Auth0 and no longer works: connections made with it ended on October 18, 2026. If you added iKnow Blockchain with the earlier ID, remove it from your app and add it again with the ID above, ikb.public, using the steps below. You only do this once.

None of these apps has been checked end to end on this address yet. If a sign-in fails, email [email protected] with the app’s name and version. Goose and Zed will be listed once their sign-in has been checked.

Cline

Cline’s documentation does not cover a client ID yet; these steps follow its source code.

In the Cline panel, choose the MCP Servers icon, open Configure and choose Configure MCP Servers (the Cline CLI uses ~/.cline/data/settings/cline_mcp_settings.json). Add this, inside "mcpServers" if the file already has one:
```
{
  "mcpServers": {
    "iknow-blockchain": {
      "type": "streamableHttp",
      "url": "https://mcp.iknowblockchain.com/mcp",
      "oauthClient": {
        "clientId": "ikb.public"
      }
    }
  }
}
```
Sign in when Cline opens the sign-in page in your browser. In the Cline CLI, run cline mcp and choose Authorize OAuth.
Run the connection check.

App documentation: Cline: MCP servers (external site) · Cline source: client ID setting (external site) · Cline source: sign-in ports (external site)

Cursor

Install in Cursor (opens the app)

Opens Cursor, if it is installed, with the address, the client ID and the scopes filled in. Confirm the install, then sign in when Cursor asks.

Choose Install in Cursor above and confirm the install in Cursor.
Sign in when Cursor opens the sign-in page. If none opens, check that the server is turned on under Customize in the sidebar.
Run the connection check in a chat.

Without the link: add this to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project), inside "mcpServers" if the file already has one:

{
  "mcpServers": {
    "iknow-blockchain": {
      "url": "https://mcp.iknowblockchain.com/mcp",
      "auth": {
        "CLIENT_ID": "ikb.public",
        "scopes": [
          "ikb:read",
          "offline_access"
        ]
      }
    }
  }
}

Keep the scopes listed: they ask for read access, the only access the connection grants.

App documentation: Cursor: MCP (external site) · Cursor: MCP install links (external site)

Gemini CLI

Add this to ~/.gemini/settings.json (every project) or .gemini/settings.json (one project), inside "mcpServers" if the file already has one. It fixes the sign-in return address on port 7777, so it stays the same each time:

{
  "mcpServers": {
    "iknow-blockchain": {
      "httpUrl": "https://mcp.iknowblockchain.com/mcp",
      "oauth": {
        "enabled": true,
        "clientId": "ikb.public",
        "scopes": [
          "ikb:read",
          "offline_access"
        ],
        "redirectUri": "http://localhost:7777/oauth/callback"
      }
    }
  }
}

In Gemini CLI, run /mcp auth iknow-blockchain and sign in in your browser. The browser must run on the same computer.
Run the connection check.

Gemini CLI’s documentation says that for unpaid-tier and Google One users, Gemini CLI was replaced by Antigravity CLI on 18 June 2026. Antigravity asks for a client secret as well, so it cannot use this client ID.

App documentation: Gemini CLI: MCP servers (external site)

Kilo Code

Kilo Code’s documentation does not cover a client ID yet; these steps follow its source code.

Add this to ~/.config/kilo/kilo.jsonc (every project) or kilo.jsonc in a project’s root (one project), inside "mcp" if the file already has one:

{
  "mcp": {
    "iknow-blockchain": {
      "type": "remote",
      "url": "https://mcp.iknowblockchain.com/mcp",
      "oauth": {
        "clientId": "ikb.public",
        "scope": "ikb:read offline_access",
        "redirectUri": "http://127.0.0.1:19876/mcp/oauth/callback"
      }
    }
  }
}

Kilo Code shows a notification to sign in to iknow-blockchain; choose it and sign in in your browser.
Run the connection check.

App documentation: Kilo Code: MCP (external site) · Kilo Code source: sign-in settings (external site)

Kiro

Add this to ~/.kiro/settings/mcp.json (every workspace) or .kiro/settings/mcp.json (one workspace), inside "mcpServers" if the file already has one. It fixes the sign-in return address on port 7779, so it stays the same each time:

{
  "mcpServers": {
    "iknow-blockchain": {
      "url": "https://mcp.iknowblockchain.com/mcp",
      "oauth": {
        "clientId": "ikb.public",
        "oauthScopes": [
          "ikb:read",
          "offline_access"
        ],
        "redirectUri": "http://localhost:7779/oauth/callback"
      }
    }
  }
}

Kiro opens the sign-in page when it connects; sign in in your browser.
Run the connection check.

App documentation: Kiro: MCP configuration (external site)

LM Studio

In LM Studio, open the Program tab in the right-hand sidebar and choose Install, then Edit mcp.json. Add this, inside "mcpServers" if the file already has one:

{
  "mcpServers": {
    "iknow-blockchain": {
      "url": "https://mcp.iknowblockchain.com/mcp",
      "auth": {
        "CLIENT_ID": "ikb.public"
      }
    }
  }
}

LM Studio opens the sign-in page in your browser; sign in.
Run the connection check.

LM Studio’s example also shows a client secret. This client ID has none, so leave it out.

App documentation: LM Studio: MCP (external site) · LM Studio: MCP with OAuth (external site)

MCP Inspector

The MCP Inspector is a developer tool for testing servers. It needs Node.js and runs the @modelcontextprotocol/inspector package from npm, which is not ours.

Run npx @modelcontextprotocol/inspector@latest and open the page it prints, at http://localhost:6274. Its sign-in return address follows the address bar.
Choose Streamable HTTP and paste the connection address.
In the server’s OAuth settings, enter the client ID above, and under Authorization enter the scopes ikb:read offline_access. Connect and sign in.

App documentation: MCP Inspector: server configuration (external site)

OpenCode

Add this to your opencode.json, inside "mcp" if the file already has one. It fixes the sign-in return address, so it stays the same when OpenCode changes its default:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "iknow-blockchain": {
      "type": "remote",
      "url": "https://mcp.iknowblockchain.com/mcp",
      "enabled": true,
      "oauth": {
        "clientId": "ikb.public",
        "scope": "ikb:read offline_access",
        "redirectUri": "http://127.0.0.1:19876/mcp/oauth/callback"
      }
    }
  }
}

Run opencode mcp auth iknow-blockchain and sign in in your browser.
Run the connection check.

App documentation: OpenCode: MCP servers (external site) · OpenCode source: sign-in settings (external site)

Perplexity

Open Account settings, then Connectors. Choose + Custom connector, then Remote.
Name it iKnow Blockchain, paste the connection address as the MCP Server URL and choose Streamable HTTP as the transport.
Choose OAuth for authentication, enter the client ID above and leave the client secret empty.
Optionally upload the iKnow Blockchain icon (PNG, 128 pixels, under 3 KB).
Tick the acknowledgement, choose Add, then select the connector card to sign in and turn it on.

Custom connectors depend on your Perplexity plan; in an organization, an admin may need to allow them. Perplexity’s help does not say whether the client secret may stay empty; if it asks for one, email [email protected].

App documentation: Perplexity: adding custom remote connectors (external site)

Qwen Code

Add this to ~/.qwen/settings.json (every project) or .qwen/settings.json (one project), inside "mcpServers" if the file already has one:

{
  "mcpServers": {
    "iknow-blockchain": {
      "httpUrl": "https://mcp.iknowblockchain.com/mcp",
      "oauth": {
        "enabled": true,
        "clientId": "ikb.public",
        "scopes": [
          "ikb:read",
          "offline_access"
        ],
        "redirectUri": "http://localhost:7777/oauth/callback"
      }
    }
  }
}

In Qwen Code, open the /mcp dialog, select iknow-blockchain and sign in in your browser.
Run the connection check.

App documentation: Qwen Code: MCP servers (external site)

VS Code (GitHub Copilot)

Install in VS Code (opens the app)

Opens VS Code, if it is installed, with the server ready to install: the address and the iKnow Blockchain client ID are filled in. Choose Install, then sign in when VS Code asks.

Choose Install in VS Code above. VS Code opens the server with the address and client ID filled in; choose Install.
When VS Code asks to sign in for iknow-blockchain, allow it and sign in in your browser.
In Copilot Chat, check that the iKnow Blockchain tools are turned on, then run the connection check.

Without the link: run MCP: Open User Configuration from the Command Palette and add this; if the file already has "servers", add only the iknow-blockchain entry inside it:

{
  "servers": {
    "iknow-blockchain": {
      "type": "http",
      "url": "https://mcp.iknowblockchain.com/mcp",
      "oauth": {
        "clientId": "ikb.public"
      }
    }
  }
}

App documentation: VS Code: MCP developer guide (external site) · VS Code: MCP configuration (external site)

Apps that only run local servers (mcp-remote)

Some apps can only start a program on your computer, not reach a server address. The open-source mcp-remote bridge connects them. It needs Node.js and runs the latest mcp-remote package from npm, which is not ours.

Add this to the app’s MCP settings file, inside "mcpServers" if the file already has one. The 3334 fixes the sign-in return port, so it stays the same each time:

{
  "mcpServers": {
    "iknow-blockchain": {
      "command": "npx",
      "args": [
        "mcp-remote@latest",
        "https://mcp.iknowblockchain.com/mcp",
        "3334",
        "--static-oauth-client-info",
        "{\"client_id\":\"ikb.public\"}",
        "--static-oauth-client-metadata",
        "{\"scope\":\"ikb:read offline_access\"}"
      ]
    }
  }
}

Restart the app. mcp-remote opens the sign-in page in your browser; sign in.
Run the connection check.

App documentation: mcp-remote (external site)

Other apps

An app not listed here needs to support remote MCP servers with OAuth sign-in. Apps that identify themselves with their own published details, as Claude, ChatGPT and Grok do, need no client ID. Our sign-in service does not offer automatic registration. If the app asks for a client ID, enter the connection address, the client ID above, no client secret and the scopes ikb:read offline_access. If the sign-in reports a redirect error, the app is not on our list yet: email [email protected] with its name.

Amazon Quick, Copilot Studio, Gemini Enterprise and Microsoft 365 Copilot are set up by an organization’s admin, and each needs its own sign-in settings on our side. To ask for one, email [email protected].

Menu names and settings files change between app versions; the app’s own documentation is linked under each app.