Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.enginy.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Enginy MCP lets you connect an AI assistant to your Enginy workspace so it can look things up, summarize what it finds, and help you prepare work inside Enginy. If you are in sales ops, rev ops, or another non-technical role, start with Claude Code first. It is the clearest setup path. The hosted resource server is: 
https://openapi.enginy.ai/mcp
Behind the scenes, Enginy MCP uses a hosted remote MCP server and a browser sign-in flow. Its tools are generated from Enginy’s public API, which helps keep MCP aligned with the rest of the product.

MCP Overview

Learn how the hosted server, OAuth flow, OpenAPI-derived tools, and workspace policy model fit together.

Connect Claude Code

Register the hosted server in Claude Code, complete OAuth, and verify the granted scopes.

Clients & interfaces

Get connection guidance for Claude, Codex, Cursor, VS Code, ChatGPT developer mode, and other remote MCP clients.

Client support matrix

Compare supported interfaces, setup shapes, and caveats before choosing the client you want to use.

Supported tools

See what Enginy MCP can do today, how the tool surface is generated, and what is not guaranteed yet.

Example prompts

Use practical prompts for Claude, Codex, Cursor, ChatGPT developer mode, and other MCP clients.

Scopes and policy

Review scope groups, policy ceilings, and how Enginy maps MCP permissions onto OpenAPI routes.

FAQ / known limitations

Get quick answers about current limitations and what assumptions are unsafe to make.

​
When to use MCP instead of direct HTTP

  • Use MCP when you want an AI assistant to work inside Enginy for you, without building a custom integration.
  • Use direct HTTP when an engineer is building a fixed product integration against specific Enginy API endpoints.

​
Fastest path for Claude Code

This is the recommended first setup for most teams.
  1. In Enginy, enable MCP for the workspace and allow http://localhost:3118/callback.
  2. Add the hosted server:
claude mcp add --transport http --callback-port 3118 enginy https://openapi.enginy.ai/mcp
  1. In Claude Code, open:
/mcp
  1. Authenticate in the browser and approve the requested scopes.
  2. Run mcp_whoami to confirm the granted client ID, user, and scopes.
The full MCP documentation lives in the dedicated MCP tab, not only in this quick-start guide.