MCP Assistant
Use MCP Assistant when a task needs tools from connected MCP servers, especially when many possible servers or tools may be available. Prefer MCP Assistant's discovery and routing tools instead of loading every downstream MCP tool directly into the agent context.
MCP Assistant server:
text
https://api.mcp-assistant.in/mcp
User connection page:
text
https://mcp-assistant.in/mcp
What MCP Assistant Provides
MCP Assistant provides access to 100+ MCP servers such as GitHub, Notion, Zapier, Supabase, Exa, DeepWiki, Apify, Context7 and other connected services.
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. Use this to avoid expensive LLM tool-calling loops when a task can be handled by discovering the right tools, inspecting only the needed schemas, executing a small program, and returning the final result.
Core Principle
Keep MCP tools discoverable, not always loaded.
Do not assume the agent needs every connected tool schema in context. Use MCP Assistant to search for the relevant capability, inspect only the needed schema, then execute the selected tool or workflow through the sandboxed runner.
Available MCP Assistant Tools
codemode_search_mcp_tools
Search connected MCP servers for relevant tools.
Use this first when the task may require an external service such as GitHub, Notion, Slack, Gmail, Linear, Supabase, Exa, Zapier, cloud providers, databases, or any other connected MCP server.
Search with the user's goal, not just a tool name. For example:
text
find GitHub issues by label
post a message to Slack
search the web with Exa
create a Notion page
query Supabase rows
If no relevant tools are found, tell the user they likely need to connect the relevant MCP server at:
text
https://mcp-assistant.in/mcp
codemode_get_mcp_tool_schema
Inspect the exact schema for a selected MCP tool before calling it through
.
Use this after
codemode_search_mcp_tools
returns a likely tool and before execution. Read the required parameters, optional parameters, expected result shape, and any server-specific constraints.
Do not guess parameter names for downstream MCP tools. Inspect the schema first.
Execute downstream MCP tool calls inside MCP Assistant's secure remote workbench.
Use this to call one or more selected MCP tools after inspecting their schemas. Prefer batching or chaining multiple dependent tool calls inside one
when it avoids unnecessary agent-visible intermediate results.
Good uses:
- Search GitHub issues, fetch related PRs, summarize the result.
- Query a database, filter rows, and return only the final answer.
- Search Exa, rank results, and return the most relevant sources.
- Create or update records across connected tools when the steps are clear.
- Transform, sort, deduplicate, or aggregate tool results before returning them to the agent.
Avoid using
for a long chain when the agent needs to inspect and decide after each step. In that case, run one stage, examine the result, then continue.
Workflow Automation Tools Are Different
Do not confuse saved workflow tools with ad-hoc MCP tool execution.
Use
when the user wants to execute connected MCP tools now without creating a saved workflow.
Use
only to run an existing saved workflow by
. It enqueues the saved workflow for execution. It is not the general-purpose way to call arbitrary MCP tools.
Use
only to create or update a UTC cron schedule for an existing saved workflow. It should be used when the user explicitly wants an action to run on a schedule or at a scheduled time. It is not needed for normal one-off MCP tool calls.
If the user asks to automate something for later, first create or update the saved script workflow, then use
to schedule it. If the user asks to test a saved workflow immediately, use
.
Default Workflow
- Decide whether the task needs an external MCP capability.
- Call
codemode_search_mcp_tools
- Choose the smallest set of relevant tools from the search result.
- For each selected tool, call
codemode_get_mcp_tool_schema
- Call to execute the selected tool call or workflow.
- Return the final result to the user, not every intermediate object unless it is useful.
When To Batch Tool Calls
Batch multiple calls inside
when:
- The task has three or more dependent tool calls.
- Intermediate results only exist to feed later steps.
- The result needs filtering, sorting, grouping, or transformation.
- The workflow crosses multiple MCP servers.
- Returning every intermediate result would bloat the agent context.
Do not batch when:
- The user needs to approve an action before it happens.
- The agent must inspect an intermediate result to choose the next step.
- A tool call is destructive or sends messages externally without clear user intent.
- Required parameters are missing or ambiguous.
- The user is asking to schedule a saved automation. Use the workflow scheduling tools for that instead.
Safety And Approval
Before making external changes, confirm user intent if the action is destructive, public, irreversible, or sends communication to other people.
Examples that usually need confirmation:
- Sending Slack, Gmail, Discord, or other outbound messages.
- Creating, deleting, or modifying production data.
- Closing issues, merging PRs, changing permissions, or deploying services.
- Running expensive workflows or broad data exports.
Read-only discovery, search, listing, and summarization can usually proceed without extra confirmation.
Failure Handling
If
codemode_search_mcp_tools
finds no relevant tools:
text
I could not find a connected MCP tool for this. Please connect the relevant MCP server at https://mcp-assistant.in/mcp, then I can search again.
If a selected tool schema is unclear, inspect another candidate tool or ask the user for the missing required input.
If
fails, summarize the error, identify whether it was caused by missing auth, missing parameters, unavailable server tools, or sandbox execution failure, then retry only when the fix is clear.
Example Patterns
Find A GitHub Issue And Summarize Related PRs
- Search tools for
GitHub search issues and pull requests
- Inspect schemas for the issue search and PR lookup tools.
- Run a workflow that searches issues, extracts linked PRs, fetches PR details, and returns a short summary.
Search Web And Return Ranked Sources
- Search tools for .
- Inspect the Exa search tool schema.
- Run a workflow that searches, filters low-quality results, ranks sources, and returns the best links with summaries.
Create A Notion Page From Processed Data
- Search tools for the source system and .
- Inspect schemas for both tools.
- Run a workflow that fetches source data, transforms it, then creates the Notion page.
- Return the created page URL and a concise summary.
Agent Guidance
Prefer MCP Assistant when it reduces context bloat or tool-selection complexity.
Use direct local tools or CLIs when they are already available, simpler, and do not require MCP server discovery.
Keep the agent context focused on the user task. Let MCP Assistant handle downstream tool discovery, schema inspection, execution, and result processing whenever that is the smaller interface.