Smackdab MCP Server

The Smackdab MCP Server lets an MCP-compatible AI assistant use the Smackdab Public API for you. Instead of writing HTTP requests, describe what you want the assistant to find or change.

The server includes read and write tools. It can search and retrieve data and, where the Public API supports the operation, create, update, and delete it. Your Public API token determines which Smackdab organization, branch, permissions, and plan limits apply.

Connect your AI client

Add a remote Streamable HTTP MCP server with these values:

Setting	Value
Name	Smackdab
URL	https://mcp.app.smackdab.ai/mcp
Header	Authorization: Bearer YOUR_SMACKDAB_PUBLIC_API_TOKEN

Use your MCP client's secure secret or environment-variable support for the token. Do not paste the token into a chat message, tool argument, source file, or shared configuration.

The MCP connection uses the same Public API token you would send as x-api-key in a direct API request. Do not also send an organization or branch identifier; that context comes from the token.

Your client's exact setup screen or configuration-file format may differ. In clients that accept JSON MCP configuration, the connection has this shape:

{
  "mcpServers": {
    "smackdab": {
      "type": "http",
      "url": "https://mcp.app.smackdab.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${SMACKDAB_PUBLIC_API_TOKEN}"
      }
    }
  }
}

Ask for the outcome you want

You do not need to name tools, endpoints, entity IDs, or field IDs. Describe the business task in plain language and let the assistant discover the correct Smackdab data before it acts.

For example, this request safely finds a contact and adds a private note:

In Smackdab, find the contact named Jordan Lee at Acme.

Show me the matching contact and their existing notes. If exactly one contact
matches, prepare this private note but do not add it until I confirm:
"Requested a pricing follow-up on August 8."

After I confirm and the note is added, give me the contact ID and new note ID.

Example requests include:

• “Find the Contacts entity, show me its fields, and list contacts updated since Monday.”
• “Create a note on the matching contact and mark it private.”
• “Update the status on these customer records.”
• “Show me the quote before deleting it, then ask for confirmation.”
• “Synchronize notes and entity-record changes since my last checkpoint.”

The assistant should use discovery tools before acting when it does not already have exact entity, record, or field IDs. Delete tools require explicit confirmation; review the proposed target carefully before approving the call.

Security and operating guidance

• Treat the Public API token like a password. Rotate or revoke it if it is exposed.
• Use a token with only the access the assistant needs.
• The MCP server passes requests to the Public API under your token's existing access. It does not bypass Smackdab permissions or rate limits.
• For automated workflows, state whether writes are allowed. If they are, define which records and operations are in scope.
• Keep updated_since and requested resources unchanged while following a complete sync cursor chain. Save a new checkpoint only after every page succeeds.

For endpoint schemas and response details, continue to use the Public API reference in this documentation.