Cinodes MCP server enables AI clients—such as Claude, Cursor, or custom-built SDKs—to communicate with external tools and data sources securely.
Overview
Cinode supports integrating with MCP (Model Context Protocol) server, allowing AI agents to access tools and environments directly. To connect, your client must:
Support MCP OAuth for authorisation management between your client and Prismatic.
Use Streamable HTTP transport (not
stdioor legacy HTTP SSE).
The easiest connection method uses the mcp-remote package, which manages OAuth and stores your Prismatic token securely in $HOME/.mcp-auth/.
Getting started
Before you begin, ensure you’ve created a Prismatic account. If you don’t already have one, please contact Cinode.
Visit Prismatic’s GitHub examples for full implementation samples.
Once connected, explore available tools and verify your integration using test prompts.
You will also need a Claude account.
Getting started
Authentication Methods
Our MCP server support various authentication options:
Personal API Token (recommended): You can generate a personal API token by clicking on your name in the top right corner and then My Account. On your account page, generate a client ID and secret in the API Accounts section.
Static token: Retrieved through Administration > Integrations > Tokens, it mimics a user and has an expiry date. This authentication option is only available for Administrators with the API role.
Configuration Examples
For Personal API Token authentication (recommended):
{
"mcpServers": {
"cinode": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.flows.cinode.com/mcp",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Basic CLIENT_ID:CLIENT_SECRET"
}
}
}
}
For Static Token authentication:
"mcpServers": {
"cinode": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.flows.cinode.com/mcp",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer STATIC_TOKEN"
}
}
}
}
LLM Provider Setup
Different AI providers have different setup instructions for MCP server. Refer each official documentation for your provider:
Claude Desktop: MCP setup documentation
Claude Code: MCP setup documentation
OpenAI: MCP integration guide
Claude.ai: Go to settings > Integrations > + Add integration, then use
https://mcp.flows.cinode.com/mcpCursor: MCP configuration guide
Windsurf: MCP setup instructions
VS Code: MCP integration docs
Troubleshooting
Restart your AI Agent after changing the configuration
Use an MCP Inspector to verify tool availability
Rate limiting: Cinode API limits apply. Reduce request frequency or contact Cinode Support for available packages for increased API limits
Step by step:
prismatic
behörigehter i cinode?
Using Claude Desktop
To connect Claude Desktop to Prismatic’s MCP server:
Locate or create your
claude_desktop_config.jsonfile.
{
"mcpServers": {
"cinode-mcp": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.flows.cinode.com/mcp"
]
}
},
"globalShortcut": ""
}Add the following configuration:
{ "mcpServers": { "prismatic": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.flows.cinode.com/mcp"] } } }Save your changes and restart Claude.
When prompted, grant Claude access to your Prismatic environment via the OAuth 2.0 consent screen.
After authentication, test the connection by asking Claude:
“Who am I?”
Claude will use Prismatic’s get-me tool to confirm the setup.
Using Claude Code
For Claude Code, run the following command to add Prismatic’s MCP server:
claude mcp add-json prismatic '{"type":"stdio","command":"npx","args":["-y","mcp-remote","https://mcp.flows.cinode.com/mcp"]}'Then run:
claude mcp list
This ensures successful authentication and registration.
Using Cursor
To connect Cursor to Prismatic’s MCP server:
Open or create your
mcp.jsonconfiguration file.Add the following JSON:
{ "mcpServers": { "prismatic": { "type": "stdio", "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.flows.cinode.com/mcp"], "env": {} } } }
Alternatively, you can add Prismatic MCP directly through Cursor’s interface.