Manage Accelo companies, contacts, jobs, tasks, tickets and time. Hosted by usefulapi — connect from Claude, 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": {
"accelo": {
"url": "https://accelo.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"accelo": {
"type": "http",
"url": "https://accelo.usefulapi.io/mcp"
}
}
}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.
The login page asks for your Accelo client secret, Accelo client id and Accelo deployment.
Register a service application in Accelo → Configuration → API. The deployment is the subdomain in yourcompany.api.accelo.com.
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 Accelo client secret, Accelo client id and Accelo deployment. 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 Accelo connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
list_companies | read | List companies List companies (client organizations). Accelo API: GET /api/v0/companies. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }. |
get_company | read | Get a company Fetch a single company (client organization). Accelo API: GET /api/v0/companies/{id}. Returns { meta, response }. |
list_contacts | read | List contacts List contacts (people at companies). Accelo API: GET /api/v0/contacts. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }. |
get_contact | read | Get a contact Fetch a single contact (a person). Accelo API: GET /api/v0/contacts/{id}. Returns { meta, response }. |
list_jobs | read | List jobs (projects) List jobs — Accelo "jobs" are projects. Accelo API: GET /api/v0/jobs. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }. |
get_job | read | Get a job (project) Fetch a single job (project). Accelo API: GET /api/v0/jobs/{id}. Returns { meta, response }. |
list_tasks | read | List tasks List tasks (units of work logged against an object such as a job or company). Accelo API: GET /api/v0/tasks. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }. |
get_task | read | Get a task Fetch a single task. Accelo API: GET /api/v0/tasks/{id}. Returns { meta, response }. |
list_activities | read | List activities List activities — notes, emails, calls, and meetings logged against objects. Accelo API: GET /api/v0/activities. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }. |
get_activity | read | Get an activity Fetch a single activity (note/email/call/meeting). Accelo API: GET /api/v0/activities/{id}. Returns { meta, response }. |
list_invoices | read | List invoices List invoices. Accelo API: GET /api/v0/invoices. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }. |
get_invoice | read | Get an invoice Fetch a single invoice. Accelo API: GET /api/v0/invoices/{id}. Returns { meta, response }. |
list_prospects | read | List prospects (sales) List prospects — sales opportunities in the pipeline. Accelo API: GET /api/v0/prospects. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }. |
get_prospect | read | Get a prospect (sale) Fetch a single prospect (sales opportunity). Accelo API: GET /api/v0/prospects/{id}. Returns { meta, response }. |
list_staff | read | List staff List staff (Accelo users in your deployment). Accelo API: GET /api/v0/staff. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }. |
get_staff | read | Get a staff member Fetch a single staff member. Accelo API: GET /api/v0/staff/{id}. Returns { meta, response }. |
list_issues | read | List issues (tickets) List issues — support/service tickets. Accelo API: GET /api/v0/issues. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }. |
get_issue | read | Get an issue (ticket) Fetch a single issue (support/service ticket). Accelo API: GET /api/v0/issues/{id}. Returns { meta, response }. |
accelo_request | read | Raw read request Power-user escape hatch: GET any Accelo API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Pass the FULL API path after the host, starting with a slash, INCLUDING any query string, e.g. "/api/v0/companies?_limit=1&_filters=status(1)" or "/api/v0/tasks/123". Returns { meta, response }. |
create_company | write | Create a company MUTATES Accelo data: creates a new company (client organization). Accelo API: POST /api/v0/companies (form-encoded). Returns { meta, response } with the created company. (Accelo has no separate delete tool here; to UPDATE, POST to /api/v0/companies/{id}.) |
create_contact | write | Create a contact MUTATES Accelo data: creates a new contact (a person). Accelo API: POST /api/v0/contacts (form-encoded). NOTE: a contact's company affiliation is set separately via an affiliation (POST /api/v0/contacts/{id}/affiliations), not on creation. Returns { meta, response } with the created contact. |
create_task | write | Create a task MUTATES Accelo data: creates a new task. Accelo tasks are always logged AGAINST an object (a job, company, issue, etc.), so against_type + against_id are required. Accelo API: POST /api/v0/tasks (form-encoded). Returns { meta, response }. |
create_activity | write | Create an activity (log a note/email/call) MUTATES Accelo data: logs an activity (a note, email, call, or meeting) against an object. This is the highest-value safe write — e.g. add a note/comment to a job or company. against_type + against_id say what it is logged against (required). Accelo API: POST /api/v0/activities (form-encoded). Returns { meta, response }. |
accelo_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
accelo_request_feature | Request a missing feature Tell usefulapi that the user needs something the Accelo 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. | |
accelo_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Accelo tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
accelo_cancel_subscription | Cancel the Pro subscription Cancel the caller's Accelo Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run accelo_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Accelo server only. Subscribe with accelo_upgrade (it returns a Stripe Checkout link). Cancel any time with accelo_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running accelo_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Accelo. The server calls the Accelo API with your own Accelo access, so it sees only the data that your account can see.
The login page asks for your Accelo client secret, Accelo client id and Accelo deployment. See Before you connect for where to find them.
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 Accelo client secret, Accelo client id and Accelo deployment. 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 Accelo 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 Accelo.
Yes, if you approve it. 4 of the 23 Accelo tools can create or change data. The other 19 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Accelo server only. Run accelo_usage_status to see how many calls you used.
Ask the AI to run accelo_upgrade: it returns a Stripe Checkout link. To cancel, run accelo_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 accelo_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, 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.