EIGENN.
docsguidesapichangelogpricingsign in
EIGENN.

MCP

Connect an MCP client to scoped Eigenn finance tools over a remote, OAuth-discoverable endpoint.

Eigenn has a remote Model Context Protocol endpoint for approved finance retrieval and selected writes:

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

The endpoint uses streamable HTTP. OAuth-capable clients can discover Eigenn's authorization and token endpoints automatically.

Connect a Client

VS Code supports a native HTTP server entry:

{
  "servers": {
    "eigenn": {
      "type": "http",
      "url": "https://api.eigenn.io/v1/mcp"
    }
  }
}

Claude Desktop and Cursor can bridge a remote HTTP server through mcp-remote:

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

The equivalent command is:

npx -y mcp-remote https://api.eigenn.io/v1/mcp

Follow the client's OAuth prompt. Then choose the correct Eigenn team. A programmatic MCP client can also use the same Authorization bearer header as the REST API.

Scope Controls

The MCP endpoint accepts a connection only when the credential includes at least one MCP-compatible scope. Eigenn then registers only the tools that the granted scopes cover.

Examples include:

  • search.read
  • customers.read and customers.write
  • invoices.read and invoices.write
  • transactions.read
  • reports.read
  • bank-accounts.read
  • documents.read
  • tracker-entries.read and tracker-entries.write
  • teams.read

A 403 response means that the credential authenticated but does not include a compatible scope. A 401 can mean that the credential or the team context is not present.

Use a read-only key or OAuth grant for analysis workflows. Add a write scope only when the client must do that specific write.

Tools, Resources, and Prompts

The granted scopes control which of these tools Eigenn shows:

  • search of finance records
  • customers
  • invoices, products, templates, and recurring invoices
  • transactions and categories
  • bank accounts
  • documents and inbox items
  • reports
  • tags
  • team context
  • tracker projects, entries, and timers

Static or team-scoped resources can include transaction categories, tags, and team information. Built-in prompts cover financial health checks, invoice follow-up, expense analysis, and customer insights.

Use the client's tool inspector to see the current list. The discovery tools can also help a client find less common read operations. Do not assume that every internal product action is available.

Approval Boundary

MCP scopes are the server-side access control. The endpoint does not add a universal human-approval step around every tool call.

For sensitive work:

  1. Grant read scopes first.
  2. Turn on the client's own confirmation controls.
  3. Make a person examine each proposed customer, invoice, cash, or ledger change.
  4. Grant a write scope only for the bounded action.
  5. Examine the Eigenn record after the action runs.

Do not describe an MCP client as read-only when its credential includes customer, invoice, or tracker write scopes.

Product Workflow Boundary

The MCP server does not show public CRUD operations for Eigenn's workflow builder or workflow execution history. Use the Workflows product area to build and check product workflows.

MCP can still support a bounded process that AI helps. Examples are an invoice follow-up summary and an examination of unusual transactions. The process uses only the records that its scopes cover.

Troubleshoot

The client cannot discover authentication

Confirm that the server URL is exactly https://api.eigenn.io/v1/mcp and that the client supports remote streamable HTTP or mcp-remote.

The connection returns 401

Authenticate again. Then confirm that the OAuth grant or the API key belongs to an accessible team.

The connection returns 403

Create or update a restricted credential with at least one compatible scope. Add only the resource scopes that the workflow needs.

A tool is not present

Compare the requested operation with the granted scopes. Eigenn does not register the tools whose resources are outside the grant.

A product workflow operation is not present

Eigenn expects this. Eigenn does not document workflow builder and execution operations as public MCP tools.

Related Pages

  • MCP Workflows
  • Authentication
  • Developer Platform
  • Workflows API Status

Integrations

Connect external systems through the App Marketplace, examine their permissions, and manage connection health safely.

SDKs

Use generated TypeScript, Python, Go, or Rust clients that follow Eigenn's public OpenAPI v1 contract.

On this page

Connect a ClientScope ControlsTools, Resources, and PromptsApproval BoundaryProduct Workflow BoundaryTroubleshootThe client cannot discover authenticationThe connection returns 401The connection returns 403A tool is not presentA product workflow operation is not presentRelated Pages

Eigenn docs

current product

Overview
Overview
OverviewAccount PreferencesAssistant AutomationAssistant Command CenterBank ConnectionsBilling and UsageBudgets and ForecastCommand CenterCustomer LifecycleCustomer RecordsCustomersDeveloper PlatformDocument Processing and ExtractionDocument VaultFinancial Analytics and ReportsFinancial OverviewInvoice InsightsInvoice ProductsInvoicesMarketplace IntegrationsNotifications and BrandingOnboarding and SupportOverviewReceivablesReceivables AnalyticsReceivables ControlsSecurity and AccessSettings OverviewStress TestsTeams and OrganizationsTone Profiles and ExperimentsTransaction Categories and RulesTransactionsWeekly Finance RitualWorkflow ExecutionsWorkflow PausesWorkflowsWorkspace Inbox and Approvals
OverviewBuild and Review a ForecastBuild Your First WorkflowConfigure Assistant OperationsConfigure Notifications and BrandingConfigure Receivables ControlsConnect Transaction RecordsCreate and Manage CustomersCreate and Send InvoicesDeveloper API SetupFirst Cash ReviewInvoice Collection WorkflowMaintain Transaction RulesManage Security and BillingManage Team AccessManage the Invoice LifecycleMCP WorkflowsMonitor and Recover WorkflowsOrganize and Share DocumentsProcess Inbox ItemsReconcile and Categorize TransactionsReview a Customer Finance RecordRun a Finance Operating ReviewRun a Receivables Tone ExperimentRun a Runway Stress TestRun Your First Command Center ReviewSet Up a WorkspaceTroubleshoot Account AccessWebhook DeliveryWeekly CFO Review
OverviewIntegrationsMCPSDKsWebhooks
OverviewAuthenticationBank Accounts APICustomers APIErrorsForecasts and Stress Tests APIInvoice Payments APIInvoices APIPaginationRate LimitsRemote Tracker API StatusTracker Categories APITracker Entries and Timers APITracker Projects APITransactions APIWebhooks API StatusWorkflows API Status
Overview
Overview