attio-mcp-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is attio-mcp-server?

attio-mcp-server is a server designed for Attio, an AI-native CRM, enabling MCP clients to connect to the Attio API for various functionalities.

how to use attio-mcp-server?

To use the attio-mcp-server, you need to set up your environment with an ATTIO_API_KEY, which can be obtained through the Attio API Explorer or by configuring OAuth.

key features of attio-mcp-server?

  • Reading company records
  • Reading company notes
  • Writing company notes
  • Integration with MCP clients like Claude

use cases of attio-mcp-server?

  1. Connecting AI clients to the Attio CRM for data retrieval and manipulation.
  2. Automating note-taking and record management in a CRM environment.
  3. Enhancing CRM functionalities through AI integrations.

FAQ from attio-mcp-server?

  • What is required to run attio-mcp-server?

You need Node.js, npm, git, and dotenv installed, along with an Attio API key.

  • Can I contribute to the development of attio-mcp-server?

Yes! You can fork the repository, clone it, and set up your development environment as per the instructions provided.

  • Is there support for other activities beyond reading and writing notes?

Currently, the server supports reading and writing company records and notes, with potential for more features in the future.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

14 hours ago