MCP Workflows

An MCP workflow combines an AI client with the Eigenn records allowed by its credential. Start with a read-only task, inspect every exposed tool, and add write access only after the review process is proven.

Choose a Bounded Task

Good first workflows include:

• prepare a financial health summary
• rank overdue invoices for follow-up
• analyze expense patterns
• summarize customer payment context
• investigate transactions that need review

Avoid starting with open-ended instructions such as managing all finance operations. Define the records, time period, output, reviewer, and actions that are out of bounds.

1. Create the Credential

1. Open Settings → Developer.
2. Create a restricted API key or configure an OAuth application.
3. Grant only the read scopes needed by the task.
4. Store a key in a server-side secret manager when the client requires one.

Example read-only grants:

The MCP endpoint accepts any connection with at least one compatible scope, but individual tools appear only when their required scopes are present.

2. Connect the Client

Use the remote endpoint:

https://api.eigenn.io/v1/mcp

Clients with native remote MCP support can use that URL directly. Claude Desktop and Cursor can use mcp-remote:

{
  "mcpServers": {
    "eigenn": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.eigenn.io/v1/mcp"
      ]
    }
  }
}

Complete the OAuth prompt when the client opens it, then confirm the selected team.

3. Inspect the Exposed Tools

Before sending business data to a prompt:

1. open the client's tool inspector
2. record the available Eigenn tools
3. confirm there are no write tools outside the task
4. inspect resources such as team information, categories, or tags
5. choose a built-in prompt or write a bounded instruction

Built-in prompt templates include:

• financial_health_check
• invoice_followup
• expense_analysis
• customer_insights

Tool availability can differ between credentials because it follows scopes.

4. State the Review Contract

Include these constraints in the task:

• the exact date range and team
• the records the client may read
• the format of the answer
• which calculations require source citations
• which actions require a person
• which actions are prohibited

Example:

Review unpaid and overdue invoices for this team.
Use invoice and customer read tools only.
Return a table with invoice ID, customer, amount, due date, and suggested next step.
Do not change records or draft customer messages.
Flag missing data instead of guessing.

5. Verify the Output

The reviewer should:

1. compare record IDs with Eigenn
2. confirm currencies and date ranges
3. distinguish missing data from zero values
4. verify calculations against source records
5. reject recommendations that require unavailable context
6. record the approved next action outside the model response

6. Add a Write Scope Only When Needed

Some MCP domains can expose selected customer, invoice, or tracker writes. The server does not wrap every tool call in a universal approval gate.

Before granting a write scope:

• enable the client's confirmation feature
• limit the credential to one resource
• test against non-production or reversible data
• make the write idempotent where the operation supports it
• verify the resulting record in Eigenn
• keep a separate read-only credential for analysis

Product Workflow Boundary

MCP does not expose public tools for creating Eigenn product workflows, triggering workflow runs, or reading workflow execution history. Build and monitor those processes in Workflows.

An MCP-assisted review can prepare inputs for a product workflow, but the two are not the same execution system.

Troubleshooting

The connection returns 403

The credential has no MCP-compatible scope. Add the smallest read scope needed by the task.

A required tool is missing

Compare the tool's resource with the key or OAuth grant. Reconnect after changing scopes.

The client can write when it should only read

Revoke or rotate the credential with read-only scopes. Client prompts are not an access-control boundary.

The answer lacks source context

Ask for record IDs and dates in the output, then verify them in Eigenn before approving an action.

Related Pages

• MCP
• Authentication
• Workflows
• Workflows API Status