# GoCanvas Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## GoCanvas

Read and create mobile forms, dispatches and submissions for field service teams

- Record: https://musedirectory.ai/connector/gocanvas
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/gocanvas/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 213ms, checked 2026-10-29T23:21:09Z
- Endpoint: https://gocanvas.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T23:21:09Z)
- Source: Found in the official MCP Registry (io.usefulapi/gocanvas) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fgocanvas

Connects to GoCanvas field service platform. Muse can read forms, submissions, users, departments, dispatches and reference data; create and manage job dispatches sent to field workers' mobile devices.

Example request: "Create a dispatch for a technician to inspect a customer site tomorrow at 10 AM with the service form pre-filled"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use GoCanvas to help me. It is a free service with an MCP server at https://gocanvas.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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.

Screening checks:
- MCP handshake: pass (Answered in 213ms)
- Domain against threat feeds (Cloudflare security DNS): pass (gocanvas.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (23 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)