codat
Server Details
MCP server for Codat — companies, connections, invoices, bills and financial statements.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.9/5 across 23 of 28 tools scored. Lowest: 3.2/5.
Each tool targets a distinct operation (create, get, list, refresh) on a specific resource (company, connection, financial statement, invoice, etc.). No two tools have overlapping purposes; even similar verbs like 'list' are paired with unique entity names, and the refresh tools are clearly differentiated by scope (all vs specific data type).
All tools follow a consistent 'codat_verb_noun' pattern (e.g., codat_create_company, codat_list_invoices, codat_get_balance_sheet). Verbs are predictably used (create, get, list, refresh), and nouns are in lowercase with underscores. The only outlier is 'codat_request' which still fits the prefix pattern and serves a distinct purpose.
The server exposes 28 tools, which covers the core Codat API operations (companies, connections, financial reports, accounting entities, data refresh). While this is on the higher end, each tool corresponds to a meaningful endpoint. A few could be consolidated (e.g., get_data_info/status) but the count remains justified for the scope of the platform.
The read and data-management surface is comprehensive (most list/get endpoints are covered), but write operations for accounting data (create/update invoices, bills, etc.) are absent. Codat's API does support these mutations, so this is a notable gap. Additionally, tools for deleting companies or connections are missing, though that may be intentional. The escape hatch partially mitigates gaps.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!