GoCanvas MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://gocanvas.usefulapi.io/mcp

claude mcp add --transport http gocanvas https://gocanvas.usefulapi.io/mcp

{
  "mcpServers": {
    "gocanvas": {
      "url": "https://gocanvas.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "gocanvas": {
      "type": "http",
      "url": "https://gocanvas.usefulapi.io/mcp"
    }
  }
}

https://gocanvas.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• gocanvas_get_me

  The user who owns the connected OAuth application: id, login, company id and name, default department and role. Use it to learn the default department id.

• gocanvas_list_forms

  Forms (mobile form definitions) the connected user can see: id, name, status, version, department. Paged, 100 per page. Use gocanvas_get_form for a form's fields (entries).

• gocanvas_get_form

  One form definition, including its screens and entries (field ids and labels). Use format 'flat' for the simplest list of fields (what you need to read submissions or create a dispatch), 'nested' (default) for the full structure, 'metadata' or 'minimal' for less.

• gocanvas_list_form_reports

  The report (PDF) definitions attached to a form: id, name, format, whether emailed by default. Paged.

• gocanvas_list_submissions

  Completed forms (submissions): id, form, number, created time, department, user, status. At least one of form_id, user_id or user_email is required (user_id and user_email cannot be combined). Default status is completed. Dates filter created_at. Paged, 100 per page. Use gocanvas

• gocanvas_get_submission

  One submission with all its responses (entry id, label, type, value). Accepts the numeric submission id or the client GUID.

• gocanvas_list_submission_revisions

  The revision history of a submission (who changed it and when). Paged.

• gocanvas_list_users

  Users of the company: id, name, email, enabled. Paged, 100 per page.

• gocanvas_get_user

  One user by id: name, login, contact data, default department and role.

• gocanvas_list_departments

  Departments of the company: id, name, description. The pseudo department -1 'All' is included.

• gocanvas_list_department_users

  The users in one department with their department role.

• gocanvas_list_dispatches

  Dispatches (jobs sent to field workers): id, form, assignee, status, schedule. At least one of user_id, department_id or form_id is required. Dates are ISO-8601. Paged.

• gocanvas_get_dispatch

  One dispatch by id with its pre-filled responses, schedule and status.

• gocanvas_list_customers

  Customers (contacts of the Project Management view): individuals or businesses, optionally tied to a site. Paged.

• gocanvas_list_projects

  Projects of the Project Management view. Paged.

• gocanvas_list_sites

  Sites (job locations) of the Project Management view. Paged.

• gocanvas_list_reference_data

  Reference data (lookup tables used by forms): id, name, columns, version. Without department_id the user's default department is used.

• gocanvas_get_reference_data

  One reference data set with its rows.

• gocanvas_list_groups

  User groups: id, name, and the forms and users assigned. Paged.

• gocanvas_list_workflows

  Workflows (handoff chains between users) the connected user takes part in, with their handoff states and the count of tasks available to claim. Paged.

• gocanvas_list_locations

  GPS location events of field users (needs the tracker feature). start_date and end_date are required and may span at most 7 days. Omit user_id for all users of the company. Paged.

• gocanvas_create_dispatch

  WRITE: creates a dispatch, a job that appears on the assignee's mobile device (immediate_dispatch is sent at once, with a push notification when send_notification is true; scheduled_dispatch needs scheduled_at and scheduled_end). Responses pre-fill the assignee's form (entry ids

• gocanvas_mark_dispatch_received

  WRITE: acknowledges a dispatch (status becomes received). Only works for a dispatch in the assigned state that is assigned to the connected user; repeating it is refused by GoCanvas.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 153 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 23 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32455 servers in this category
• Published to the registry more recently than 97% of the other 32455 servers in this category
• Basic checks equal to or better than 100% of the other 32455 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{