Skip to main content

Overview

The local MCP server is an open-source Python package you run on your own machine over stdio. You authenticate once with your Chift API credentials, and unlike the remote server it can work across all of your consumers rather than a single one. It is built for builders: if you have a Chift account with several consumers and you want an assistant that helps you configure Chift and explore the Unified API across them, the local server is the right tool. It also offers an optional documentation search tool that brings the entire Chift documentation into your coding assistant’s context. The source code is available on GitHub.

Prerequisites

  • A Chift account with API credentials (client ID, client secret, and account ID).
  • Python 3.11 or higher.
  • The uv package manager.
More detail on prerequisites is available in the project README.

Installation

The server runs with uvx, which fetches and launches the package in one step:
You normally do not run this by hand. Your MCP client launches it for you using the configuration in Connecting your client. Set your credentials as environment variables first (see Configuration).

Configuration

The server reads its configuration from environment variables (prefixed with CHIFT_), which you can set in your MCP client configuration or a local .env file.
Leaving CHIFT_CONSUMER_ID unset is what makes the local server useful to builders: the assistant can discover and work across every consumer on your account. Set it when you want to pin a session to one consumer.

Connecting your client

IDE configuration

Add the following to your claude_desktop_config.json:

Using with AI frameworks

When running locally you integrate the server over stdio transport.

Function configuration

By default, all operations are enabled for every domain:
Set the CHIFT_FUNCTION_CONFIG environment variable to restrict which operations are exposed per domain, for example to give an assistant read-only access. More detail is available in the project README.
Function configuration is specific to the local server. The remote server uses OAuth scopes to control which operations are available.
The local server can expose a SearchChift tool that searches the entire Chift documentation like a vector database: pass a query and retrieve the documentation passages that match semantically. It brings Chift documentation directly into your coding assistant’s context, which helps it integrate Chift faster. The tool is off by default. Enable it by setting: