mcp-assistant

MCP Assistant MCP Assistant provides access to 100+ MCP servers like GitHub, Notion, Zapier, Supabase, etc.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • List Mcp Servers: List all connected MCP servers and the number of tools each provides. Use this when `search_mcp_tools` returns no response or irrelevant results, to see if there is an active/connect
  • Search Mcp Tools: Search connected MCP tools for the authenticated user and return normalized discovery results. Use this to find candidate MCP tools before execution. Next, pass the chosen result to
  • Get Mcp Tool Schema: Retrieve a normalized schema payload for a connected MCP tool. Use this to inspect the exact input schema, output schema when available, and the CodeMode result extraction hint. T

What data it sees

Do you need an account

No: the server works without sign-in

MCP Assistant

MCP Assistant provides access to 100+ MCP servers like GitHub, Notion, Zapier, Supabase, etc.

  • Connect & Manage Integrations: You can configure and connect these integrations/connectors directly from the MCP Assistant Dashboard.
  • Advanced Features: It exposes meta-tools for dynamic MCP discovery and a CodeMode tool that executes programs inside a secure sandbox for programmatic tool calling, workflow execution, and result processing, avoiding expensive LLM tool-calling loops.

Endpoint

Use this URL with your Assistant such as (OpenCode, Cursor, Codex, ClaudeCode, Antigravity etc.):

https://api.mcp-assistant.in/mcp

Key Features

  • Unified Gateway: Access 100+ third-party integrations (GitHub, Notion, Zapier, Slack, Discord, Supabase) through a single endpoint.
  • Dynamic Tool Discovery: Run semantic searches across all connected tool schemas.
  • CodeMode Sandbox: Execute JavaScript/TypeScript scripts on the server side using the @mcp-ts/codemode secure sandbox. Run multi-step programmatic workflows or batch actions directly from a single LLM request to avoid expensive round-trips.
  • Standard OAuth Authentication: Fully compatible with client-side OAuth handlers—log in securely via your browser to authorize access to your integrations.

Primary Tools Provided

Tool Description
search_mcp_tools Performs a semantic/phrase search across all your connected tools and returns normalized discovery results.
get_mcp_tool_schema Retrieves the exact input/output JSON schemas and execution helper details for any tool.
codemode_run Instantly executes a script inside the CodeMode sandbox to chain multiple tool calls, format outputs, or filter large responses.
list_mcp_servers Lists all connected MCP servers and the number of tools each provides.

Client Configuration

VS Code

Add the server connection to your VS Code settings:

{
  "servers": {
    "mcp-assistant": {
      "type": "http",
      "url": "https://api.mcp-assistant.in/mcp"
    }
  }
}

Cursor / Antigravity / Claude Desktop

Add to your client configuration file:

{
  "mcpServers": {
    "mcp-assistant": {
      "url": "https://api.mcp-assistant.in/mcp"
    }
  }
}

How to connect

How to connect mcp-assistant to Claude

The server address to paste into Claude settings:

https://mcp_assistant--zonlabs.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect mcp-assistant to ChatGPT

The server address to paste into ChatGPT settings:

https://mcp_assistant--zonlabs.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect mcp-assistant to Cursor

The server address to paste into Cursor settings:

https://mcp_assistant--zonlabs.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (4)

Raw names from tools/list. Only developers need these.

list_mcp_serversList all connected MCP servers and the number of tools each provides. Use this when `search_mcp_tools` returns no response or irrelevant results, to see if there is an active/connected server that might be relevant.
search_mcp_toolsSearch connected MCP tools for the authenticated user and return normalized discovery results. Use this to find candidate MCP tools before execution. Next, pass the chosen result to `get_mcp_tool_schema` to inspect the exact schema, then call the tool from `codemode_run` or a saved workflow script.
get_mcp_tool_schemaRetrieve a normalized schema payload for a connected MCP tool. Use this to inspect the exact input schema, output schema when available, and the CodeMode result extraction hint. Then call that MCP tool from `codemode_run` or a saved workflow script once the args match the schema.
codemode_runExecute a JavaScript/TypeScript-like script in the CodeMode sandbox with connected MCP tool servers. No queue, workflow, or schedule required. Use this when `search_mcp_tools` or `get_mcp_tool_schema` identified an MCP tool, or when any equivalent MCP tool-discovery and schema-inspection tools identified one, and you want to inspect its output or validate its schema usage quickly without creating a saved workflow. This is also the right tool for chaining multiple MCP tool calls in one script, avoiding repeated agent loops and context reduction, handling batch processing, or transforming, filtering, or summarizing large tool call results before returning them. Recommended flow: First search for the right MCP tool with `search_mcp_tools`. Then inspect that tool's schema with `get_mcp_tool_schema`, or use any equivalent search/schema tools provided by the current MCP client. Finally execute the real MCP call from this script once the args match the schema. When using `callTool(serverId, toolName, args)` or namespaced helpers, the sandbox returns the normalized tool result directly. Use raw helpers only when you explicitly need the MCP envelope.