Skip to main content
Alpha: this page reflects the current MCP surface, but tool coverage, tool names, and exact input shapes can still change as Enginy’s public OpenAPI surface evolves.

​
What this page covers Alpha

This page answers a simple question: what can an AI assistant realistically help with in Enginy today? Enginy MCP does not ship a separate hand-written tool catalog. Instead, the MCP server reads Enginy’s public API document and turns supported API operations into MCP tools. That means the MCP surface stays aligned with the public API. The current MCP server also exposes one native tool:
  • mcp_whoami, which returns the authenticated user, client, and granted scopes

​
What an assistant can help with today Alpha

The current surface is broad enough for real operator workflows. Representative capability families include:
Capability familyRepresentative things you can do
WorkspaceRead workspace metadata, credits, saved views, filters, and validation helpers
IdentitiesInspect sender identities and identity performance
OwnersLook up CRM owners for routing and assignment flows
CampaignsRead campaigns and folders, create campaigns, clone campaigns, and change campaign state
ContactsSearch contacts, read contact fields, create contacts, and update contacts
CompaniesSearch companies, read company fields, create companies, and update companies
ListsRead lists and folders, create or update list structures, and move members
AI variablesRead AI variables and folders, create or update them, and delete them
AnalyticsRead analytics exports and campaign analytics
ActionsInspect action-run state and trigger action-style workflows such as imports
MessagingRead inbox threads, tags, and conversation messages; send replies; mutate thread state
WebhooksRead webhook subscriptions and logs, and create, update, delete, or test webhooks
In practice, what the assistant can successfully do depends on two things: whether the action exists in the public API, and whether the approved permissions allow it. If a tool exists but your permissions are too narrow, the call will be blocked when the assistant tries to use it.

​
Advanced: how tool inputs are shaped Alpha

OpenAPI-derived tools follow a simple input pattern: 
{
  "pathParams": {
    "id": "123"
  },
  "query": {
    "limit": 25,
    "includeArchived": false
  },
  "body": {
    "name": "Example"
  }
}
In practice:
  • pathParams holds route parameters
  • query holds query-string arguments
  • body holds JSON request bodies
The tool name usually comes from the OpenAPI summary. If names would collide, Enginy falls back to a method-plus-path style name.

​
What is not guaranteed yet Alpha

  • Tool names can change if the OpenAPI summary changes.
  • Coverage changes whenever Enginy’s public API surface changes.
  • Some operations may not be available if they are not part of the public contract.
  • mcp_whoami is the only native MCP tool today; the rest are generated from OpenAPI.
  • The MCP server is remote Streamable HTTP only. It is not a local stdio server.

​
What to try first

If you are deciding whether the alpha is useful for your workflow, start with:
  1. mcp_whoami to confirm the connection and granted scopes.
  2. The overview page to understand the transport and policy model.
  3. The scopes page to see which permission families unlock which tools.
  4. The client setup page if you need Claude, Codex, Cursor, or VS Code wiring.

Overview (Alpha)

Review the hosted server model, OpenAPI-derived tool generation, and runtime policy enforcement.

Clients & interfaces (Alpha)

See how to connect Enginy MCP from Claude, Codex, Cursor, VS Code, ChatGPT developer mode, and more.

Scopes (Alpha)

Match the tool families above to the scope groups that unlock them.

Security & troubleshooting (Alpha)

Debug auth, scope, and compatibility problems before assuming the server is broken.