eavz

MCP Tool Mode

Set up MCP servers in TOOLS mode to expose integration actions as individual tools for AI agents.

TOOLS mode MCP servers expose each integration action as an individual tool. AI agents like Claude, Cursor, and others see every action as a separate callable tool with its own typed input schema.

Create an MCP Server

1

Navigate to MCP Servers

Open the dashboard and go to MCP Servers in the sidebar.

2

Create a new server

Click Create MCP Server. Enter a name and optional description.

3

Select TOOLS mode

Choose TOOLS as the server mode.

4

Save and copy credentials

Click Create. Copy the bearer token and SSE endpoint — you'll need these to connect your AI client.

Add Tools

Each tool maps to one integration action. You can add tools from different integrations to the same server.

1

Open your MCP server

Go to MCP Servers and click on the server you created.

2

Add a tool

Click Add Tool. Select an integration (e.g. Slack, GitHub) and pick the action you want to expose.

3

Set a connection

Choose the connection that this tool should use for authentication.

4

Save

Click Save. The tool is now available to any AI client connected to this server.

Tool Naming Convention

Tools are automatically named using the pattern {integrationAlias}__{actionName}:

IntegrationActionTool Name
slacksend_channel_messageslack__send_channel_message
githubcreate_issuegithub__create_issue
google-sheetsread_sheetgoogle_sheets__read_sheet

You can register the same integration multiple times under different aliases (e.g. slack_bot, slack_user), each with its own connection. See the Integration Aliases guide.

MCP Helper Tools

For actions with select inputs — like selecting a Slack channel or a GitHub repo — Weavz auto-generates companion tools that let AI agents discover valid values at runtime.

Helper ToolPurpose
slack__list_channelsList available Slack channels
github__list_reposList available GitHub repositories
google_sheets__list_spreadsheetsList available spreadsheets

Helper tools are created automatically whenever you add a tool that has dropdown inputs. The AI agent calls them to resolve IDs before executing the main action.

Connect an AI Client

Use the SSE endpoint and bearer token from the server creation step.

Add to your Claude Desktop config (claude_desktop_config.json):

json
{
  "mcpServers": {
    "weavz": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.weavz.io/api/v1/mcp/servers/mcp_abc123/sse",
        "--header",
        "Authorization:Bearer mcp_token_xyz..."
      ]
    }
  }
}

Managing Tools

bash
curl -X PATCH https://api.weavz.io/api/v1/mcp/servers/mcp_abc123/tools/tool_xyz \
  -H "Authorization: Bearer wvz_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "description": "Send a message to a Slack channel",
    "inputDefaults": { "channel": "C01ABCDEF" }
  }'
bash
curl -X DELETE https://api.weavz.io/api/v1/mcp/servers/mcp_abc123/tools/tool_xyz \
  -H "Authorization: Bearer wvz_your_api_key"

If a token is compromised, regenerate it and update your AI client config:

bash
curl -X POST https://api.weavz.io/api/v1/mcp/servers/mcp_abc123/regenerate-token \
  -H "Authorization: Bearer wvz_your_api_key"

End-User MCP Servers

You can scope an MCP server to a specific end user by passing endUserId when creating the server. The server will resolve connections belonging to that end user, so an AI agent automatically uses their connected accounts.

bash
curl -X POST https://api.weavz.io/api/v1/mcp/servers \
  -H "Authorization: Bearer wvz_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "User Agent",
    "workspaceId": "proj_abc123",
    "endUserId": "user_123",
    "mode": "TOOLS"
  }'

When a tool call fails because the end user hasn't connected the required integration, the error includes a setup URL. Share this URL with the end user — they open it, connect their account, and the agent can retry the tool call.

When to Use TOOLS Mode

TOOLS mode works best when:

  • You need a small number of focused tools (under 20)
  • Each tool should be independently callable by the AI agent
  • You want simple setup without code generation
  • Your AI agent benefits from seeing all available tools at once

For scenarios with many integrations or where context efficiency matters, consider CODE mode instead.