Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
execute_codeA

Execute TypeScript/JavaScript code to perform MCP operations efficiently.

Token Savings: 90-98% vs individual tool calls. Batch operations in a single execution.

API: mcp.server('name').call('tool', params) | mcp.searchTools('query') | mcp.log('msg')

Example: const files = await mcp.filesystem.call('list_directory', { path: '/src' }); return files;

Use passthrough_call only for debugging - it has HIGH token cost.

list_serversB

List all MCP servers connected through MCP Executor.

discover_toolsA

Search for available tools across all connected MCP servers.

get_metricsA

Get detailed aggregated metrics for the current session including token savings, performance, and usage patterns.

set_modeA

Switch between operation modes:

  • execution: All requests go through the code executor (default, maximum token savings)

  • passthrough: Direct tool calls without code execution (for debugging/comparison)

  • hybrid: Automatic selection based on task complexity

reload_serversA

Reload MCP server configurations. Useful after modifying claude_desktop_config.json.

get_capabilitiesA

Get detailed information about MCP Executor capabilities and configuration.

compare_modesA

Analyse how a task would be handled in different modes. Returns estimated token usage and approach for each mode.

passthrough_callA

⚠️ DEBUGGING TOOL - Direct MCP tool call. HIGH TOKEN COST (10-100x vs execute_code).

Only use for debugging raw tool input/output. Use execute_code for all normal operations.

brave_web_searchA

Web search via Brave Search API. Uses 90% fewer tokens than native WebSearch.

Routes to brave-search MCP server internally. Requires brave-search server to be configured.

add_serverA

Add a new MCP server to conductor config and connect immediately.

Saves the server configuration to ~/.mcp-conductor.json and triggers a reload. Use this to dynamically add servers without restarting Claude.

remove_serverA

Remove an MCP server from conductor config and disconnect it.

Removes the server configuration from ~/.mcp-conductor.json and triggers a reload. Use this to dynamically remove servers without restarting Claude.

update_serverA

Update an existing MCP server's configuration (command, args, or env vars).

Use this to update API keys or other settings without removing and re-adding the server. Triggers a reload to apply changes immediately.

get_memory_statsA

Returns live memory usage and resource counts for the conductor process. Use this to diagnose memory issues.

predict_costA

Predict the token cost and latency of executing code based on historical samples for similar call patterns.

get_hot_pathsA

Return the top-K tool call paths by total latency or p99 within a rolling time window.

record_sessionA

Start recording all tool calls in the current session to a replay journal.

stop_recordingA

Stop an active recording session and finalise the replay journal.

replay_sessionA

Replay a recorded session, optionally applying modifications. Detects divergence when replayed result differs from recorded result.

import_servers_from_claudeA

Import MCP servers from Claude config files into ~/.mcp-conductor.json.

Reads ~/.claude/settings.json, ~/Library/Application Support/Claude/claude_desktop_config.json and other standard paths. Shows a diff of what will be imported. On confirm=true, copies entries into the conductor config and writes .bak backups of each source file. Optionally strips the imported servers from their source configs.

test_serverA

Transiently connect to a named MCP server from conductor config, list its tools and measure latency. Does NOT persist the connection or register the server. The server must be present in ~/.mcp-conductor.json.

diagnose_serverA

Diagnose a registered MCP server: process health, connection status, recent errors, reconnect attempts, last successful call, and registry state. Returns actionable information about why a server may be failing.

recommend_routingA

Apply the X1 routing heuristic to one or all configured servers. Servers whose names match lightweight-payload patterns (search, calendar, email, etc.) are recommended as "passthrough". All others default to "execute_code" (safe default). Use apply=true to write the hints into conductor config.

export_to_claudeA

Generate a mcpServers JSON block that points Claude back at mcp-conductor stdio. This is the rollback path: paste the output into your Claude Desktop or Claude Code config to restore direct connectivity. Formats: "claude-desktop" (full wrapper object), "claude-code" (flat mcpServers), "raw" (inner object only).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/darkiceinteractive/mcp-conductor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server