MCP.so
Sign In

Official Ampersand AI SDKs MCP Server

@amp-labs

Basic information

Category

Other

License

MIT

Transports

stdio

Author

amp-labs

About Official Ampersand AI SDKs MCP Server

Official AI SDK by Ampersand

Official Ampersand AI SDKs MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Official Ampersand AI SDKs MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Official Ampersand AI SDKs?

This repo contains the official Ampersand AI SDK and the official MCP server for Ampersand. The AI SDK exposes tools for AI agents to manage and interact with integrations with customers' SaaS tools, while the MCP server exposes those tools via the Model Context Protocol.

How to use Official Ampersand AI SDKs?

Install the AI SDK with npm install @amp-labs/ai (or yarn/pnpm). Import modules such as createRecord and updateRecord from framework-specific paths (e.g., @amp-labs/ai/aisdk for Vercel AI SDK, @amp-labs/ai/mastra for Mastra). For the MCP server, configure it in mcp.json or claude_desktop_config.json using either SSE mode (with URL and headers/query param) or stdio mode (with npx command and env variables).

Key features of Official Ampersand AI SDKs

  • AI SDK provides tools like createRecord and updateRecord.
  • MCP server connects agents to 150+ Ampersand connectors.
  • Supports Vercel AI SDK, Mastra, and other agent frameworks.
  • Multi-tenant MCP server exposes Ampersand primitives as native tools.
  • Includes end-to-end tests for the AI SDK.
  • MIT licensed and open to contributions.

Use cases of Official Ampersand AI SDKs

  • Build AI agents that create, update, and manage records in customer SaaS tools.
  • Verify Salesforce connections via the checkConnection tool in AI workflows.
  • Integrate B2B SaaS integrations into agentic apps using the Ampersand platform.
  • Test and iterate on local SDK changes with the provided test infrastructure.

Frequently asked questions

1

What runtime or dependencies are required for the MCP server?

The MCP server can be run via SSE (remote) or stdio (local). For stdio, you need Node.js and `npx`. Environment variables include `AMPERSAND_API_KEY`, `AMPERSAND_PROJECT_ID`, `AMPERSAND_GROUP_REF`, and optionally `AMPERSAND_INTEGRATION_NAME`.

2

How do I authenticate with the remote MCP server?

Pass your Ampersand API key via the `x-api-key` header in SSE mode, or as a query parameter (`apiKey`) if headers are not supported. For stdio mode, set it in the `env` as `AMPERSAND_API_KEY`.

3

Where is the data or integration configuration stored?

Ampersand manages integrations and connectors on its platform; the SDK and MCP server reference your project, integration, and group (identified by `projectId`, `integrationName`, and `groupRef`) to access the appropriate configuration.

4

What transport modes does the MCP server support?

The MCP server supports SSE (Server-Sent Events) for remote clients and stdio for local clients (e.g., via `npx`).

Comments

More Other MCP servers