Addepar MCP
Ask Claude about Addepar holdings, performance, exposure, transactions and private fund capital calls.
Ask Claude about Expensify expenses, reports, receipts and spending trends.
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
The Expensify MCP server lets Claude search and analyse your Expensify data: expenses, reports, reimbursements, receipts, trips and spending trends. Anthropic's directory lists three tools, built around a single Search. Expensify documents it as read-only, so Claude cannot approve a report, edit an expense or send a reimbursement. You connect with OAuth.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Search does the work, so the directory's three tool names do not show which record types or filters it supports. We could not read its schema.Yes. Expensify's help article says Owners in Claude can make the connector available to their whole organization, and it points to Claude's instructions for organization-wide connectors on Team and Enterprise plans. Each member still signs in with their own Expensify account through OAuth, so what Claude can search follows each person's own Expensify access rather than the Owner's.
The OAuth approval most likely did not complete. Expensify's first check is to confirm you finished the approval flow in your browser. If access still fails, its next steps are to verify the MCP server URL, restart the connector, and reauthorize the OAuth connection, which re-runs the sign-in and usually clears an expired or half-finished authorization.
No. Expensify states that the MCP server is read-only. Claude can search and summarise expenses, reports, receipts and spending, but approving reports, editing expenses, reimbursing payments and managing Workspace settings stay in the Expensify app. Asking Claude to make one of those changes will not change anything in Expensify, because no tool on this connector can do it.
Remove it in Claude's connector settings. Expensify's article defers to Claude's own documentation on removing custom connectors rather than describing a step inside Expensify. Removing the connector stops Claude from reaching your Expensify data in new conversations; it does not change anything in your Expensify account, since the connector never had write access in the first place.
initialize probe — https://www.expensify.com/mcp returned HTTP 308 to https://www.expensify.com/mcp/, which returned an HTTP 401 authentication challenge with scope="mcp:tools" and resource_metadata at https://www.expensify.com/.well-known/oauth-protected-resource/mcp (2026-11-18). The root descriptor form returned Expensify's HTML 404 page. · retrieved 2026-11-18https://www.expensify.com/.well-known/oauth-authorization-server (fetched 2026-11-18; scopes mcp:tools and integrations:api) · retrieved 2026-11-18anthropic-directory-2026-11-17.json) · retrieved 2026-11-17Connect Expensify once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.