Connect a client

Point your client at https://api.isearchfrom.com/mcp, complete a one-time browser sign-in, and your agent can use iSearchFrom’s tools. The steps below cover the most common clients; any spec-compliant MCP client that supports Streamable HTTP + OAuth works the same way.

Before you start

• You need an iSearchFrom account whose organization has the MCP feature enabled. If it isn’t, the connection fails at sign-in with a clear “feature not enabled” message — check Plans, tokens & limits or upgrade in the app.
• The server URL is the same for every client: https://api.isearchfrom.com/mcp.
• There is no API key to paste — the client discovers the OAuth endpoint from the URL and opens a browser for you to sign in and pick an organization.

Set up your client

Claude Code

Add the server with the Claude Code CLI:

claude mcp add --transport http isearchfrom https://api.isearchfrom.com/mcp

The first time a session uses a tool, Claude Code opens your browser to sign in and authorize. Verify it registered:

claude mcp list

You should see isearchfrom listed. Remove it any time with:

claude mcp remove isearchfrom

Claude Desktop

Recent Claude Desktop versions support remote servers as custom connectors:

Open connector settings

Go to Settings → Connectors → Add custom connector.

Add the server

Give it a name (iSearchFrom) and paste the URL https://api.isearchfrom.com/mcp.

Authorize

Claude Desktop opens a browser window. Sign in, choose the organization the agent should act in, and approve the permissions. The connector then shows as connected.

Older versions

If your version has no custom-connector UI, use Claude Code or another client below — the hosted server is identical regardless of client.

Cursor

Add the server to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project:

{
  "mcpServers": {
    "isearchfrom": {
      "url": "https://api.isearchfrom.com/mcp"
    }
  }
}

Open Cursor Settings → MCP, confirm isearchfrom appears, and click to authorize when prompted. Cursor opens the browser sign-in and stores the resulting token for you.

Cline

In VS Code, open the Cline MCP settings (Cline → MCP Servers → Configure) and add a remote server:

{
  "mcpServers": {
    "isearchfrom": {
      "url": "https://api.isearchfrom.com/mcp",
      "transportType": "streamableHttp"
    }
  }
}

Reload the server list; Cline prompts you to authorize in the browser on first use.

Any MCP client

For any spec-compliant client that supports Streamable HTTP transport and OAuth:

• Server URL: https://api.isearchfrom.com/mcp
• The client should perform OAuth discovery against https://api.isearchfrom.com/.well-known/oauth-protected-resource, register itself, and open a browser for you to sign in and consent.
• No client secret or API key is required — the server issues a token scoped to the organization and permissions you approve.

If your client cannot do the OAuth flow (for example, a stdio-only agent), see the OpenClaw guide for a bridge pattern.

The one-time authorization

However you add the server, the first tool call triggers the same flow:

Sign in

The client opens https://app.isearchfrom.com in your browser. Sign in if you aren’t already.

Choose an organization

If you belong to more than one organization, pick which one the client should act in. Every tool the agent runs happens inside that organization and spends its tokens.

Approve the permissions

The consent screen shows exactly what the client is asking for. Approve to finish, or cancel to abort. The client stores the resulting token and reuses it for future sessions.

Grant the least you need

If you only want the agent to run searches and read results, approve a read/search-scoped grant and nothing more. The agent physically cannot call tools outside its grant, and you can revoke the connection at any time.

Verify it works

Ask your agent something that exercises a read-only tool first — it’s free and confirms the connection end to end:

Using iSearchFrom, who am I connected as and what's my current token balance?

The agent calls whoami and get_token_balance and reports your user, organization, and balance. Then try a real search:

Using iSearchFrom, run a Google search for "best crm software" as a mobile user in
Germany (country DE, language de) and summarise the top 3 organic results and any ads.

Troubleshooting

Symptom	Likely cause	Fix
Browser sign-in never opens	Client didn’t complete OAuth discovery	Confirm the URL is exactly https://api.isearchfrom.com/mcp; check the client supports HTTP + OAuth.
”Feature not enabled” after sign-in	Organization’s plan doesn’t include MCP	Enable MCP on the plan or switch to an organization that has it. See Plans, tokens & limits.
Agent can’t see a tool you expected	Your grant or role doesn’t include it	Re-authorize with the needed permission, or check your role. See Permissions & security.
Tool returns “no read access granted”	query_sql/describe_schema need read scope	Grant read on the relevant data when you authorize the client.
Searches return errors about balance	Not enough tokens	Top up or check usage — see Token top-ups.
429 / rate limited	Agent looped too fast	Bound the agent’s loops; limits are documented in Errors, pagination & rate limits.

Related

Tool catalogEvery tool the agent can call.

Permissions & securityScopes, token spend, and revoking a connection.

OpenClawConnect a self-hosted OpenClaw agent.