MCP Workflows

An MCP workflow combines an AI client with the Eigenn records that its credential permits. Start with a read-only task. Examine every tool that the client shows. Add write access only after you prove the review process.

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

Do not start with an open-ended instruction such as one to manage all finance operations. Define the records, the time period, the output, the reviewer, and the actions that are out of bounds.

1. Create the Credential

1. Open Settings → Developer.
2. Create a restricted API key, or set up 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 needs one.

Example read-only grants:

The MCP endpoint accepts any connection that has at least one compatible scope. But each tool appears only when its necessary 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. Examine the Available Tools

Before you send business data to a prompt:

1. Open the client's tool inspector.
2. Record the available Eigenn tools.
3. Confirm that there are no write tools outside the task.
4. Examine 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 that the client can read
• The format of the answer
• The calculations that need source citations
• The actions that need a person
• The actions that you prohibit

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. Confirm the Output

The reviewer must:

1. Compare record IDs with Eigenn.
2. Confirm currencies and date ranges.
3. Separate missing data from zero values.
4. Check calculations against source records.
5. Reject recommendations that need unavailable context.
6. Record the approved next action outside the model response.

6. Add a Write Scope Only When Needed

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

Before you grant a write scope:

• Turn on 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
• Check the record that results in Eigenn
• Keep a separate read-only credential for analysis

Product Workflow Boundary

MCP does not give public tools that create Eigenn product workflows, that start workflow runs, or that read workflow execution history. Build and watch those processes in Workflows.

A review that uses MCP can prepare inputs for a product workflow. But the two are not the same execution system.

Troubleshoot

The connection returns 403

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

A necessary tool does not appear

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

The client can write when it must 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 check them in Eigenn before you approve an action.

Related Pages

• MCP
• Authentication
• Workflows
• Workflows API Status