Overview
The Chift Model Context Protocol (MCP) defines a set of tools you can use to build AI Agents that can interact with the different integrations offered by Chift and search in our documentation through one MCP server. It exposes the Chift Unified API to any LLM provider supporting the MCP protocol like Claude, Cursor or Windsurf. Chift MCP server can be found here.Getting Started
You can use the Chift MCP server in two ways:- Remote Server (Recommended) - Connect directly to our hosted MCP server
- Local Installation - Install and run the server locally
Remote Server (Recommended)
The remote server is the easiest way to get started with Chift MCP. No local installation required!Prerequisites
- A Chift account with client credentials (client ID, client secret, account ID, and consumer ID)
Getting an Access Token
To use the remote server, you first need to obtain an access token by making a POST request tohttps://api.chift.eu/mcp-token
:
Required Parameters
Your Chift client ID
Your Chift client secret
Your Chift account ID (UUID format)
Your consumer ID (UUID format)
Optional environment ID (UUID format)
Optional marketplace ID (UUID format)
IDE Configuration
- Claude Desktop
- Cursor
- VS Code
- Claude Code
Configure Claude for Desktop to use the remote MCP server:
Replace
<your_mcp_access_token>
with the token received from the /mcp-token
endpoint.Setup Steps
- Get your MCP access token using the API call above
- Choose your preferred IDE from the tabs above
- Either use the one-click install link or manually add the configuration
- Replace
<your_mcp_access_token>
with your actual token - Restart your IDE/application
- You should see the Chift tools available in the chat interface
The remote server setup is complete! You can now use Chift MCP tools in your
chosen IDE without any local dependencies.
Local Installation
You can also run the MCP server locally in astdio
environment. Local installation is ideal if you want better AI support during integration of the Chift API. Running the MCP server locally allows you to:
- Choice between limiting the MCP server to a specific consumer or allowing access to all
- Search and reference the entire Chift Documentation directly from your IDE for improved AI context when
- Customize your setup for specific workflows
Prerequisites
- A Chift account with client credentials (client ID, client secret, account ID, and consumer ID)
- Python 3.11 or higher
- uv package manager
Installation Steps
- Install the required dependencies (Python 3.11+ and uv)
- Install the Chift MCP server package
- Configure your environment variables
- Set up your client configuration
IDE Configuration
- Claude Desktop
- Cursor
- VS Code
- Claude Code
This is an example configuration for Claude Desktop when using local installation:
Setup Steps
- Install Python 3.11+ and uv on your system
- Install the Chift MCP server:
uvx chift-mcp-server@latest
- Set up your environment variables (see below)
- Choose your preferred IDE from the tabs above and add the configuration
- Replace the credential placeholders with your actual values
- Restart your IDE/application
- You should see the Chift tools available in the chat interface
Environment Variables for Local Installation
The following environment variables are required for local installation:Local installation is complete! You now have full control over your MCP server
instance and can use Chift MCP tools in your chosen IDE.
Other LLM Providers
The Chift MCP server works with any LLM provider that supports the MCP protocol, not just Claude Desktop. We have elaborated on several examples (PydanticAI, Copilot, …) hereAvailable Tools
The Chift MCP Server dynamically generates tools based on the Chift OpenAPI specification. These tools provide access to various Chift API endpoints and include operations for:- Retrieving financial data
- Managing your financial connections
- Creating new financial records (invoices, payments, etc.)
- Updating existing records
- And much more…
Advanced Configuration
Function Configuration (Local Installation Only)
For local installations, you can customize which operations are available for each domain. By default, all operations are enabled for all domains:CHIFT_FUNCTION_CONFIG
environment variable. More details can be found here.
Function configuration is only available for local installations. The remote
server provides access to all available operations.