MCP: overview and access

MCP (Model Context Protocol) lets an AI assistant use the octoja data and tools you authorize. The connection belongs to your octoja user and does not extend its device or customer access. No API key is required.

Choose your next step

Prerequisites

You need an octoja user and an MCP client supporting servers over Streamable HTTP with OAuth sign-in.

Your group needs MCP Usage, assigned under Administration → Groups. It permits connecting and using MCP, but does not replace the permissions and device actions required by individual tools. Removing it blocks MCP access even for an existing connection.

Use a model with strong tool-calling support, such as current GPT and Claude models. Even capable models can make mistakes: review target devices and intended changes before approving an action.

Connect another MCP client

1. Open Settings → MCP clients → Add MCP client in octoja.
2. Copy the displayed server address. It ends in /mcp.
3. Add a remote MCP server in your AI tool using that address, Streamable HTTP transport and OAuth authentication. octoja supports automatic client registration; you do not need to create an API key or enter an OAuth client secret.
4. Start the connection, sign in to octoja and review the requested access. Approve only what the assistant needs for its task.
5. Return to MCP clients. After completing the OAuth connection, the client appears with Authorized by, Connected and Last used.

Review access

Click the permission badge beside the client name to see the granted access.

Start with View octoja data for a read-only test. Add further access only for a specific task. Screen contents and retrieved data are sent to your AI client; consider your organization's data-handling rules before connecting it.

Regular users see and manage their own authorizations. Administrators can also see and disconnect other users' authorizations.

Disconnect a client

1. Open Settings → MCP clients.
2. Open Actions → Disconnect in the client's row.
3. Check the client name and confirm Disconnect.

The associated access and refresh tokens are revoked immediately. Linked file-archive downloads lose their authorization and computer-use sessions close too. The client must authorize again to reconnect. Disconnecting does not undo actions already performed.

FAQ

Why can my assistant read data but not run a device action?

Check the client's granted access under Settings → MCP clients and your octoja user's permissions for the intended action. Read access alone does not authorize changes.

If a required grant is missing, disconnect and reconnect the client to approve it. If the tool itself is missing from your assistant, refresh its tool list or reconnect it.