Read relations, invoices, tasks and documents; create tasks and log interactions in AdminPulse. For accountants and bookkeepers who manage client files in AdminPulse. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"adminpulse": {
"url": "https://adminpulse.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"adminpulse": {
"type": "http",
"url": "https://adminpulse.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
List the tasks with a deadline in a date range. Open one task to read its status, deadline and relation.
adminpulse_list_tasks adminpulse_get_task
Find the client by name. List its sales invoices, filtered by paid status, and open one to read its lines and payment status.
adminpulse_find_relations_by_name adminpulse_list_invoices adminpulse_get_invoice
Find the client and log the call, meeting or note with its date and time. List the interactions afterwards to check the entry.
Changes data · adminpulse_find_relations_by_name adminpulse_add_interaction adminpulse_list_interactions
Find the client, then create a task with a deadline. Update the task status when the work is done.
Changes data · adminpulse_find_relations_by_name adminpulse_create_task adminpulse_update_task_status
List the document metadata of a client, such as name, type, date and tags. The server does not upload documents.
adminpulse_find_relations_by_name adminpulse_list_documents
The login page asks for your AdminPulse API key.
Create the key in AdminPulse under My profile → Access tokens. Only an administrator can create one. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your AdminPulse API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the AdminPulse connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
adminpulse_get_current_user | read | Get the connected user Return the AdminPulse user that the API key belongs to (name and email). Good first call to confirm the connection. GET /users/me. |
adminpulse_list_companies | read | List companies List the companies (administrations) that this key can access, with their ids. GET /companies. |
adminpulse_search_relations | read | Search relations List relations (clients, suppliers and contacts) with paging. Filter by text, relation type (0 company, 1 sole proprietor, 2 person), tags, or include inactive. GET /relations. |
adminpulse_get_relation | read | Get a relation Get one relation with its details. Pass the relation GUID or its unique identifier such as APR00001. GET /relations/{identifier}. |
adminpulse_find_relations_by_name | read | Find relations by name Quick lookup of relations by name, returning a short list with their ids and unique identifiers. GET /relations/names. |
adminpulse_list_invoices | read | List invoices List sales invoices with paging. Filter by relation, invoice date range, or sent, paid, exported and draft status. GET /invoices. |
adminpulse_get_invoice | read | Get an invoice Get one invoice by its id (GUID), with its lines and payment status. GET /invoices/{invoiceId}. |
adminpulse_list_tasks | read | List tasks List tasks with paging. Filter by relation id, deadline range, or main task template. GET /tasks. |
adminpulse_get_task | read | Get a task Get one task by its id (GUID), with its status, deadline and relation. GET /tasks/{taskId}. |
adminpulse_create_task | write | Create a task Create a task for a relation. The deadline is ISO, for example 2026-01-31T00:00:00. Status is the number the API defines. POST /tasks. |
adminpulse_update_task_status | write | Update a task status Set the status of a task found by relation, deadline and task names (no task id needed). Setting the same status again changes nothing. POST /tasks/updateStatus. |
adminpulse_list_interactions | read | List interactions List logged interactions (calls, meetings, notes) with paging. Filter by relation, type or date. GET /interactions. |
adminpulse_add_interaction | write | Log an interaction Log an interaction (for example a call or a note) on a relation. The date is ddMMyyyy and the time is HH:mm. POST /interactions/add. |
adminpulse_list_registrations | read | List registrations List time or cost registrations with paging. Filter by relation, invoiced state or registration date range. GET /registrations. |
adminpulse_list_documents | read | List documents List document metadata (name, type, dates, tags) with paging. Filter by relation or document date range. GET /documents. |
adminpulse_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
adminpulse_request_feature | Request a missing feature Tell usefulapi that the user needs something the AdminPulse tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
adminpulse_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on AdminPulse (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
adminpulse_cancel_subscription | Cancel the Pro subscription Cancel the caller's AdminPulse Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run adminpulse_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this AdminPulse server only. Subscribe with adminpulse_upgrade (it returns a Stripe Checkout link). Cancel any time with adminpulse_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running adminpulse_upgrade before then undoes the cancel. Or write to [email protected].
Find tasks with a deadline in a week. Check the invoices of a client. Log a call or meeting on a client file. Create a follow-up task for a client. Review the documents stored for a client. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by AdminPulse. The server calls the AdminPulse API with your own AdminPulse access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your AdminPulse API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your AdminPulse API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the AdminPulse API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in AdminPulse.
Yes, if you approve it. 3 of the 15 AdminPulse tools can create or change data. The other 12 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this AdminPulse server only. Cancel any time: Pro then runs to the end of the paid period. Run adminpulse_usage_status to see how many calls you used.
Ask the AI to run adminpulse_upgrade: it returns a Stripe Checkout link. To cancel, run adminpulse_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with adminpulse_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.