- Home
- MCP servers
- Superface
Superface
- javascript
4
GitHub Stars
javascript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"superfaceai-mcp": {
"command": "npx",
"args": [
"-y",
"@superfaceai/mcp"
],
"env": {
"SUPERFACE_API_KEY": "<YOUR_API_KEY>"
}
}
}
}You can run Superface MCP Server to access and manage Superface tools through the Model Context Protocol. This server lets you connect your MCP client to remote tooling with a secure API key and flexible runtimes, so you can leverage your chosen tools inside your MCP workflows.
How to use
You use the MCP server by configuring your MCP client to connect via a local stdio host or a remote execution environment. Start by selecting your preferred execution method and providing the required API key. Once configured, your MCP client can call into Superface tooling to perform model-driven actions, fetch data sources, and execute available actions across your connected tools.
How to install
Prerequisites you need before installing:
- Node.js and npm (for NPX-based runtime)
- Docker (for the Docker-based runtime, if you prefer containerized execution)
Install steps using NPX runtime:
1. Prepare your environment with Node.js and npm.
2. Create or update your MCP client configuration to use NPX runtime and reference the Superface MCP package.
3. Insert your API key into the configuration.
Install steps using Docker runtime:
1. Ensure Docker is installed and running.
2. Create or update your MCP client configuration to run the Superface MCP package inside Docker.
3. Set your API key in the environment for the container.
Build
docker build -t mcp/superface .
Configuration tips
Configure the MCP client with one of the available runtimes. You can run the server via NPX to pull the package on demand, or run it inside Docker for a containerized environment. In either case, provide your API key to authorize access to your Superface tools.
Security notes
Protect your API key. Do not share it publicly or commit it to version control. Use environment variables in your local machine or deployment environment to pass the API key securely to the MCP runtime.