INTEGRATIONGuide

Connect an AI client to Movitera MCP

Use Movitera MCP to query and update your workspace from an external AI client without copying credentials or granting more access than your account already has.

Before you start

  • An active Movitera® account and access to the team you want to query.
  • A client that supports remote MCP servers, such as Claude, Cursor, ChatGPT, or another compatible client.
  • A recent second-factor confirmation. Movitera asks for this verification before approving the connection.
  • The Movitera MCP URL: https://api.movitera.com/mcp.
  • If you use Cursor, follow **Connect Cursor** below instead of pasting the URL alone.

Connect by URL

  1. 1

    In the AI client, add a remote MCP server.

    When the client asks for the server URL, paste https://api.movitera.com/mcp.

  2. 2

    Sign in to Movitera when the browser opens.

    Authorization happens in the browser. Sign in normally and complete the security check when prompted.

  3. 3

    Choose the team and approve the connection.

    The authorization screen shows which client is requesting access. Review it before approving. The connection is limited to the team you choose; to query another team, add another connection and approve it for that team. If the client asks for write access, leave Allow changes (recommended) checked so it can make changes, or uncheck it to connect read-only. Then choose Allow.

  4. 4

    Return to the AI client.

    result
    The client can now query the Movitera areas your account can access. If you allowed changes, it can also make the changes your account can already make.

Connect Cursor

Cursor's built-in remote MCP flow often opens a blank browser page (about:blank) or a prompt to open Cursor before the Movitera authorize screen appears. Use the config below so authorization runs through a local proxy Cursor handles reliably.

  1. 1

    Open **Cursor Settings → Tools & MCP** (or edit `~/.cursor/mcp.json`).

  2. 2

    Add this server:

    json
    {
      "mcpServers": {
        "movitera": {
          "command": "npx",
          "args": ["-y", "mcp-remote", "https://api.movitera.com/mcp"]
        }
      }
    }
  3. 3

    Save, then reload MCP servers if Cursor does not pick up the change.

  4. 4

    Click **Connect** on the `movitera` server.

  5. 5

    When the browser opens the Movitera authorize page, sign in, complete the security check, choose the team, and choose **Allow**. If Cursor asks for write access, leave `Allow changes (recommended)` checked, or uncheck it to connect read-only.

    result
    Cursor lists Movitera tools, and the agent can query the areas your account can access for that team. If you allowed changes, it can also make the changes your account can already make.

**Requirements:** Node.js available on your PATH so npx can run. The first connect may download mcp-remote.

Understand the authorization screen

The authorization screen shows who is requesting access, what the connection will be able to do, and which team it will see. Check each item before choosing Allow or Deny.

Screen itemWhat it means
DestinationThe address that receives access when you approve. Confirm it matches the client you are connecting.
This app will be able toWhat the connection can do. The screen currently shows these items in Portuguese. Ler dados (Read data) covers what your account can already see in this team: Wiki, tickets, issues, initiatives, activities, suppliers, assets, and monitors. When the client asks for write access, the screen also shows Fazer alterações (Make changes): creating drafts, replying to tickets, changing status, and other actions. Those changes run only if you leave Allow changes (recommended) checked.
TeamThe team whose data the connection sees. The list shows only teams where you are an active member. To query another team, create another connection.
Connection name (optional)The name that identifies this connection in Access tokens. If you leave it empty, Movitera uses MCP · followed by the client name. Use a name that identifies the device, such as Claude on my laptop.
Allow changes (recommended)Shows up when the client asks for write access, and starts checked. While it is checked, the client makes the changes your account allows without asking you to confirm each one, until you revoke access. Uncheck it to connect read-only. The list Only in the Movitera app, never over MCP: names what no MCP client can do: Create a vendor, Mark invoice as paid, and Update a vendor.
This request expires inCountdown for the approval window, about 10 minutes. When it reaches zero, the screen shows This request expired. Start the connection again from the client.

Unidentified app

When the client does not identify itself, the screen shows Connect an app to Movitera and the warning We couldn't confirm this app's name. Continue only if you started this connection yourself. Approve only if you just started the connection in that client. When in doubt, choose Deny.

What to ask the client

  • Ask for a Wiki runbook or policy before answering from general knowledge.
  • Ask it to summarize tickets, issues in Projects, today's tasks, supplier contracts, or assets assigned to you.
  • Use date, status, owner, supplier, or category filters when you want a smaller list.
  • If you allowed changes when you connected, the client can also create and update items, such as replying to tickets, changing status, or creating issues and Wiki drafts, without asking you to confirm each one. If you connected read-only, the client sends you a link to allow changes in the browser when it needs them.

Shortcuts

Some MCP clients also show resources for attaching tickets, Wiki pages, issues, initiatives, activities, suppliers, or assets as context, and prompts such as /triage-ticket, /triage-ticket-to-issue, /on-hold-briefing, /suggest-wiki-for-ticket, /define-initiative, /breakdown-initiative, /weekly-supplier-review, /onboard-asset, /quick-create-activity, and /setup-status-monitoring.

Areas the client can query

AreaExample uses
WikiFind pages, runbooks, policies, and team documentation.
TicketsQuery tickets, conversations, categories, and open requests.
ProjectsQuery issues, initiatives, cycles, designs, domains, and initiative definitions.
TasksList today's tasks, activities, and categories.
ContractsQuery suppliers, contracts, invoices, and expiration dates.
InventoryQuery assets, assigned equipment, warranties expiring soon, and Movitera Link computers with their memory, CPU, disk, and antivirus.
UptimeQuery monitors, incidents, and the status page overview.
UsersFind people in the workspace when a question depends on an owner, requester, or team member.

Vault stays outside MCP

Vault credentials, passwords, tokens, and keys are not exposed through MCP. To view a secret, open the credential in Vault.

Write better questions

  • Name the area the client should query: Wiki, Tickets, Projects, Tasks, Contracts, Inventory, or Uptime.
  • Include filters you would use in Movitera, such as period, status, supplier, owner, or category.
  • Ask the client to cite the records it used when you need to verify the source.
  • For team processes, ask it to search Wiki first and then summarize the result.

How access stays limited

  • Every tool revalidates your user and module permissions before returning data.
  • Without access to Projects, for example, Projects tools do not appear in your client. The catalog the client sees reflects your permissions.
  • The client makes changes only after you allow them in the browser, either on the authorization screen with Allow changes (recommended) checked or later through the link the client sends. The permission lasts until you revoke it and does not ask you to confirm each action.
  • Marking an invoice as paid, creating a supplier, and updating a supplier work only in the Movitera app, never through an MCP client.
  • MCP has no access to Vault. Passwords, tokens, and keys are never exposed.

Manage or revoke access

  • Approving creates an access token for that client and team, with the name you set in Connection name (optional). It is valid for about 90 days.
  • You can see and revoke that token in Settings → Access tokens, under the User group. See Access tokens.
  • Revoking disconnects the client immediately and also ends its permission to make changes. To use it again, connect and approve it again. To keep read access and remove only the changes, ask the client to revoke its write permission.
  • If you connected read-only and later want to allow changes, ask the client. It sends a link that opens the Allow Movitera writes for this agent page in your browser. Check the agent, the team, and the apps, then choose Allow. The request expires after 30 minutes. Requests still waiting appear under Pending write requests.

If it does not work

  • Cursor opens about:blank or asks to open Cursor.app without showing the Movitera authorize page: do not approve that prompt as the connection. Use **Connect Cursor** with mcp-remote instead of pasting only https://api.movitera.com/mcp as a remote URL.
  • The URL is not accepted: confirm that you pasted https://api.movitera.com/mcp.
  • No tools appear: confirm that the client supports remote MCP servers and reconnect the integration.
  • A tool cannot find data: confirm your module access in Movitera and try a more specific search.
  • You cannot approve: sign in to Movitera again, complete the second-factor confirmation, and select an active team.
  • This request expired: the approval window of about 10 minutes ended before you chose Allow. Start the connection again from the client; the screen opens with a new countdown.
  • This request was already handled: the link was already approved or denied, usually from an old tab. If you need a new connection, start again from the client.
  • Invalid authorization link: the link you opened is incomplete or no longer points to a valid request. Start the connection again from the client to get a new link.
  • You aren't an active member of this team. Pick another team and try again.: your membership in the chosen team is inactive. Pick another team in the Team field or ask the team admin to reactivate your access.
  • Two-factor authentication cancelled. Try again.: the security confirmation was closed before it finished. Choose Allow again and complete the check.