This MCP server provides a FastMCP-compatible interface to interact with Attio resources. It exposes a set of MCP endpoints that proxy requests to the Attio API, enabling you to manage workspace data such as contacts, organizations, and other resources through the Attio API integration. By default, the server uses Server-Sent Events (SSE) as the transport mechanism and serves its API at http://0.0.0.0:8000, with the SSE endpoint available at /sse. You can customize the transport by setting the TRANSPORT environment variable to one of: stdio, streamable-http, or sse, per deployment guidance. To begin, configure your Attio credentials in the environment (BASE_URL and API_KEY) and run the server; then use your MCP client to interact with the provided endpoints to create, read, update, and delete Attio resources as supported by the server.

Prerequisites:

• Python 3.8+ installed on your system
• Git installed
• Optional: a virtual environment tool (venv on Python is fine)

Step-by-step installation:

1. Clone the repository git clone <repository-url> cd attio-mcp

2. Create and activate a virtual environment python -m venv venv

   macOS/Linux

   source venv/bin/activate

   Windows

   venv\Scripts\activate

3. Install dependencies pip install -r requirements.txt

4. Configure environment variables Create a .env file in the project root (or export vars in your shell) with: BASE_URL=https://api.attio.com API_KEY=your_attio_api_key_here

   Alternatively, you can set them in your environment before starting the server.

5. Run the server python main.py

6. Verify operation The server should be reachable at http://0.0.0.0:8000 by default, and SSE at http://0.0.0.0:8000/sse.

Notes:

• BASE_URL should point to your Attio API endpoint. If you use a custom or regional endpoint, update BASE_URL accordingly.
• Keep API_KEY secure; do not commit it to version control.
• If you deploy behind a proxy or in a container, ensure port 8000 is exposed and the TRANSPORT option matches your client capabilities.
• If you encounter authentication errors, double-check that BASE_URL and API_KEY are correctly configured and that the Attio API key has the necessary permissions.
• Refer to the deployment guide linked in the README for details on transport options and advanced configuration.