Light

Query your company's bills, cards, expenses and ledger data.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Light connector does

The Light MCP server connects Light — an AI-native accounting and spend platform for multi-entity companies — to Claude, ChatGPT or any MCP client. Its 42 listed tools search bills, vendors, cards, expenses and tax codes against a live ledger. Thirteen write: they approve tasks, submit expenses, freeze cards and attach receipts. Access follows your Light role.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Light tools (42)

  • approve_task
  • attach_card_transaction_receipt
  • attach_files
  • create_support_ticket
  • delete_system_skill
  • delete_user_skill
  • get_batch_operation_status
  • get_bill_details
  • get_card_details
  • get_card_transaction_details
  • get_draft_expenses
  • get_help_articles
  • get_reimbursement_profile
  • get_reimbursement_status
  • get_user_details
  • google_search
  • list_documents
  • load_skill
  • modify_draft_card_transactions
  • query_policy
  • read_documents
  • read_help_article
  • search_accounts
  • search_bills
  • search_card_balance_accounts
  • search_card_transactions
  • search_cards
  • search_company_entities
  • search_custom_properties
  • search_expenses
  • search_release_templates
  • search_skills
  • search_tax_codes
  • search_user_tasks
  • search_users
  • search_vendors
  • submit_expenses
  • trigger_crm_sync
  • update_card_freeze_state
  • upsert_reimbursement_profile
  • upsert_system_skill
  • upsert_user_skill

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Your Light role governs everything. Light names role permissions as the cause when the tool list is empty or shorter than expected. There is no scope-level narrowing available, so the role is the only control surface.
  • An admin gate comes first. Accounts not enabled for MCP see no MCP Tokens section and cannot connect by either route.
  • 20 active tokens per user, and a token is shown only once at creation. Light documents revocation under Settings → Profile → MCP Tokens.
  • The listing is incomplete. Report editing, journal entries, reconciliation and purchase requests are advertised by Light and by Anthropic's own description, and appear nowhere among the 42 names. How many tools exist beyond the listing is not stated by any source we could reach.
  • No safety annotations were read. The endpoint requires OAuth, so no readOnlyHint or destructiveHint values, and no parameter schemas, are published here. The read/write split above is derived from tool names and vendor prose, not from server annotations — treat it as a reasoned classification, not a vendor assertion.
  • Two writes leave your ledger. create_support_ticket reaches Light's support team and google_search reaches the open web. Neither can be recalled from the assistant.
  • Approval is authority, not information. approve_task exercises a control step that Light's audit trail attributes to you.
  • This page describes the hosted remote connector only. Light also ships Slack, Teams and Google Sheets surfaces and a separate in-app Light Command Interface, which Light says can reverse payments and create customer credits. Those capabilities belong to LCI, not to the MCP listing, and must not be read across.

Frequently asked questions

Can the Light MCP server move money or pay a bill?

No tool in the published listing pays anything. The 42 names Anthropic's directory carries include no pay, post, transfer or payment verb, and Light's own help article steers first-time users to a read-only check. The connector reaches payables data — searching bills and vendors — rather than the payment rails that settle them.

Why does Claude show fewer Light tools than the 42 that are listed?

Your Light role does not grant access to all of them. Light's help article lists a short tool list as a known symptom and names role permissions as the cause, pointing admins at Settings then Users. The connector inherits whatever the signed-in Light account can already reach, so two colleagues can see different tool counts on the same server.

Does the Light MCP connector send my Claude conversation to Light?

No. Light states that your AI model runs on your machine, that Light receives only the individual tool calls you trigger, and that no conversation history or AI output is ever sent to Light. Tool results flow back to the assistant. The boundary is per-call, so Light sees the queries you make but not the reasoning around them.

Do I need my admin to switch on the Light MCP server first?

Yes. Light's help article says the account must be enabled for MCP and tells users to contact their account manager if the MCP Tokens section is missing from their profile. This gate applies to the built-in Claude connector too, not only to token-based clients. It is the first troubleshooting row in Light's own table.

Which Light tools can change data rather than just read it?

Thirteen of the 42 write. They approve tasks, attach receipts and files, create support tickets, modify draft card transactions, submit expenses for reimbursement, freeze or unfreeze a card, trigger a CRM sync, and create or delete stored skills. The remaining 29 search, read or look up. Only the two delete tools remove anything permanently.

What OAuth scopes does the Light MCP server ask for?

None specific to the connector. Light's RFC 9728 resource descriptor publishes an empty scopes_supported array, and its Auth0 authorization server advertises only OIDC identity claims such as openid, profile and email. There is no application scope to grant or decline, so the consent screen carries no read-only option — access falls back to your Light role.

Can I use the Light MCP server outside Claude?

Yes. Light documents a second route for clients without a built-in connector: generate a personal MCP token in Settings then Profile, and point the client at the token endpoint. Light shows worked configurations for Claude Code and OpenCode. Tokens are personal, capped at 20 active per user, and shown only once at creation.

Sources

More Finance connectors

  • Affinity

    Search your CRM, prep for meetings and update deal records from your AI assistant.

  • Aiera

    Pull earnings-call transcripts, event calendars, SEC filings and company publications into your AI assistant.

  • Airwallex Developer

    Search Airwallex documentation and exercise a sandbox account from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Light to work.

Connect Light once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio