AI assistants and MCP

Caraer supports two different MCP use cases. The public developer MCP lets an assistant discover features, search documentation, inspect OpenAPI operations, and read task instructions. The separate authenticated company MCP exposes its supported company tools under the caller’s access permissions.

Why integrate

An assistant can discover how to build your integration from the same published contract and guides your developers use. When an agent also needs to work with company data, its tools and authorization can be handled through the company connection.

What you could build

Give a coding assistant the developer MCP and ask it to find the operations and skills needed for a record-enrichment app. For an assistant that helps users with records or forms, connect the authenticated company service and discover the actual tools available to that user.

Start integrating

Connect to the developer MCP, explore canonical skills, and read authentication and permissions before working with company data. Published documentation results identify their source snapshot and canonical links.

The developer MCP is public and read-only: it does not execute Caraer API calls or grant access to a company. Skills describe tasks and preserve the need for authorization; installing a skill does not authorize writes. For the company MCP, inspect its live tool schemas and permissions rather than assuming every HTTP operation is exposed as a tool.