Connect an AI client to Lynka

Connection details

MCP endpoint

https://api.lynkacrm.com/mcp

Transport

MCP Streamable HTTP

Authentication

OAuth 2.1 bearer authorization through Lynka’s existing authorization server. Discover its current endpoints and supported scopes from the linked metadata below.

How an agent connects

1. Configure an MCP-compatible client to use https://api.lynkacrm.com/mcp.
2. Follow the OAuth protected-resource challenge and authorize the Lynka account in the existing sign-in flow.
3. Initialize the MCP connection, then call tools/list. That response provides the currently supported tool names, descriptions, input schemas and read/write annotations.
4. Call a listed tool with its documented arguments. Lynka applies the connected user’s workspace membership, record visibility and permissions.

Tool calls can read or change CRM records. Deal Won and Lost actions require explicit human confirmation. Creating a deal also requires a qualified lead; creating a quote creates a draft and does not send it.

What the tools cover

The current MCP tool set covers identity and workspace context, CRM search, leads and notes, deals and pipeline, activities and follow-ups, customers and contacts, quotes and invoices, products and services, and reports. Read the live tool schemas before calling a tool because its required fields and permissions are specific to that operation.

Machine-readable resources

• OpenAPI document

  OpenAPI 3.1 description of Lynka’s MCP Streamable HTTP JSON-RPC transport.

• MCP server descriptor

  Machine-readable endpoint, transport and authentication discovery.

• API permissions document

  Advertised OAuth scopes and the authorization model applied to MCP tools.

• OAuth protected-resource metadata

  The MCP resource’s authoritative authorization-server and scope metadata.

• OAuth authorization-server metadata

  Live discovery document for Lynka’s existing OAuth authorization server.

• Product documentation

  Guides for using Lynka CRM.