mcp

The Superface MCP Server lets you access and orchestrate Superface tools through the Model Context Protocol. By pointing your MCP client to this server and authenticating with your API key, you can dynamically load and run the Superface tools you selected in the Superface dashboard. The server exposes capabilities to execute Superface-powered tasks and return structured results suitable for integration with Claude Desktop or other MCP-enabled clients. To get started, obtain an API key from the Superface dashboard and choose a deployment method (NPX via Node.js or Docker) as shown in the README. The tools you enable in the dashboard determine what capabilities are available through MCP.

Prerequisites:

• Node.js and npm (for NPX usage) or Docker (for container usage).
• Access to the Superface dashboard to enable tools and generate an API key.

Install via NPX (recommended quick-start):

1. Ensure Node.js is installed.
2. Create an MCP config snippet (see mcp_config.npx example below).
3. Run the server by invoking npx @superfaceai/mcp with your config, or use the provided JSON configuration in Claude Desktop.

Install via Docker:

1. Ensure Docker is installed.
2. Use the Docker command from the README snippet to run the container: docker run -i --rm -e SUPERFACE_API_KEY=<YOUR_API_KEY> mcp/superface
3. Provide your MCP config to the client as shown in the examples.

Configuration example (NPX): { "mcpServers": { "superface": { "command": "npx", "args": [ "-y", "@superfaceai/mcp" ], "env": { "SUPERFACE_API_KEY": "<YOUR_API_KEY>" } } } }

Configuration example (Docker): { "mcpServers": { "superface": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "SUPERFACE_API_KEY", "mcp/superface" ], "env": { "SUPERFACE_API_KEY": "<YOUR_API_KEY>" } } } }

Notes and tips:

• Manage your API key securely; do not commit it to public repos.
• The available tools depend on what you enable in the Superface dashboard; ensure your chosen tools are activated before querying via MCP.
• If you switch between NPX and Docker, keep the environment variable name (SUPERFACE_API_KEY) consistent.
• For local testing, ensure network access to Superface services and that the API key has the necessary permissions.
• If you encounter authentication errors, double-check the API key scope and that it is correctly set in the env for your chosen deployment method.