Intelogos MCP

Connect Claude, ChatGPT, Cursor or any MCP client to Intelogos: who can connect, setup, what your assistant can read and change, and example prompts.

Intelogos MCP is a Model Context Protocol (MCP) server that connects an AI assistant you already use to your organization's Intelogos data. Once connected, the assistant can look up people, departments and projects, pull KPIs, read daily activity and work sessions, analyze application usage and check schedules and time off, then answer your questions in plain language. Owners and Admins can also let it make changes, such as categorizing a tool or approving a time-off request, and every change is confirmed before it happens.

It is a remote server run by Intelogos. You don't install or host anything: you add the server URL and your own credentials to the client.

Intelogos MCP is included in the AI Intelligence and Enterprise plans. See the pricing page for what each plan includes.


Who Can Connect

Account Owners, Admins and Managers can connect an AI client. Each person creates their own Client ID and Client Secret in Settings → MCP, and the connection acts as that person: the assistant sees only what they can see in Intelogos and can do only what their role and permissions allow. See the Settings guide for the tab itself.

  • Owners and Admins connect to read data and can also let their assistant make changes. See Letting Your Assistant Make Changes.
  • Managers connect read-only: their assistant can read what they can see, but never change anything.
  • Regular users and Deployment users can't connect. They don't see the MCP tab.

Your MCP client signs in with your credentials over OAuth 2.0. Requests without a valid token are refused, so the server URL alone gives no access to any data.


Set Up Your Client

  1. In Intelogos, open Settings → MCP. If the MCP Connection card is empty, click Generate credentials. Copy the MCP URL, Client ID and Client Secret from the card.
  2. In your AI client, open its MCP settings (called Connectors, MCP servers or Integrations depending on the client) and add a new remote server.
  3. Enter the MCP URL as the server URL and the Client ID and Client Secret as its credentials, then save.
  4. When your browser opens, sign in to Intelogos and click Allow on the approval screen. The screen shows who you're connecting as and what the client asks for: "Allow Claude to read Intelogos?" when it asks to read, or "Allow Claude to read and change Intelogos?" when it also asks to make changes on your behalf (with your client's name in place of Claude). Click Deny to cancel the connection.
  5. Return to your AI client and restart it if it asks you to. The Intelogos tools appear in the assistant's tool list once the connection is active.

The MCP tab shows the same steps with tabs for General, ChatGPT and Claude configurations.

Claude (claude.ai)

Open Settings → Connectors, choose Add custom connector and paste the MCP URL as the server URL. Enter the Client ID and Client Secret where the connector asks for the server's credentials, then save. Sign in to Intelogos when Claude asks you to connect, click Allow, and check that the connector shows as connected.

Claude Code

Add the server from the terminal, using the MCP URL from Settings → MCP:

claude mcp add --transport http intelogos <MCP URL from Settings → MCP>

Cursor

Add the server to .cursor/mcp.json in a project, or to ~/.cursor/mcp.json for every project, using the MCP URL from Settings → MCP:

{
  "mcpServers": {
    "intelogos": {
      "url": "<MCP URL from Settings → MCP>"
    }
  }
}

Claude Code and Cursor then need the Client ID and Client Secret from Settings → MCP; enter them where the client asks for the server's credentials, then sign in to Intelogos in the browser window that opens and click Allow.

ChatGPT

The ChatGPT tab in Settings → MCP walks through these steps: in ChatGPT, open Settings → Apps and turn on Developer Mode. Choose Create App, enter a name, the MCP URL, the Client ID and the Client Secret, then click Create Connection. Sign in to Intelogos, click Allow, and check that the status shows Connected.

Other clients

Add a remote MCP server with the same MCP URL and credentials in the client's MCP or connector settings. Menu names differ by client and version; the generic steps above apply everywhere.


What Your Assistant Can Access

What the assistant can read is organized in the same data groups you see on the MCP access card in Settings → MCP. A group set to None is hidden from the assistant, and within every group the assistant only sees what your own role and permissions let you see in Intelogos, including which people you manage.

Data groupWhat the assistant can read
Performance & activity analyticsKPIs, time categories, rankings, application and tool usage, and work-time and workload reports
Employee & organization directoryEmployee, department and project lists, the reporting hierarchy, and looking people up by name
Work sessions & hourly activityWork sessions, availability, hourly activity and each day's first and last activity
Chronicle reportsApp-by-app Chronicle reports and automatic project assignments. Needs "Can see detailed user activity in Chronicle"
Time offTime-off balances, policies, requests and the team calendar
Organization settingsCompany-wide settings and work-hours policies
Tool & category managementTool importance and time categories. Needs "Can change tools and category of tools"
Billing & subscriptionYour organization's Intelogos plan, licenses and billing status
Background agentsPeople tracked by background agents and their devices

See Safe Defaults for which groups are on when you first connect.


Letting Your Assistant Make Changes

A connection reads data by default. Owners and Admins can also let their assistant make changes, such as categorizing a tool, approving a time-off request or updating someone's job title. What the assistant may change is set per data group on the MCP access card in Settings → MCP, and every change is previewed and confirmed before it happens.

Access Levels

Each data group on the MCP access card has one of three levels:

LevelWhat it means
NoneThe assistant can't see this group at all. Its tools are hidden.
ReadThe assistant can read this group.
WriteThe assistant can also make the changes this group allows.

Click a group to expand it and see what it lets the assistant read (Can read) and change (Can change). The buttons at the top of the card are presets: Read sets every group to Read, Write sets every group to Write, and Customize shows None, Read and Write for each group so you can set them one by one. The last row, Destructive changes, is a separate switch with None and Allow; the presets never change it.

Data groupStarts atCan the assistant change anything here?
Performance & activity analyticsReadNo, Read is the highest level
Employee & organization directoryReadYes
Work sessions & hourly activityReadNo, Read is the highest level
Chronicle reportsReadYes
Time offReadYes
Organization settingsReadYes
Tool & category managementReadYes
Billing & subscriptionNoneNo, Read is the highest level
Background agentsNoneYes
Destructive changesNoneExtra switch for destructive changes (None or Allow)

Safe Defaults

Every data group starts at Read except Billing & subscription and Background agents, which start at None. Destructive changes starts at None, and no group starts at Write, so a new connection can read data but can't change anything.

Watch the presets. On the organization card, the Read and Write buttons set every group to that level, including Billing & subscription and Background agents. To keep those two groups at None, click Customize and set the groups one by one instead.

Who Sets Access

  • The Account Owner sees the organization card. Its levels apply to every connected AI client in the organization and are the ceiling for everyone.
  • Every other Admin and every Manager sees only their own card, which applies to the AI clients they connect. It follows the organization's levels and lists only the groups their role can reach. They can lower a group for themselves, but never raise it above the organization's level. In Settings, nobody can change someone else's card.
  • Some groups depend on permissions set on the person's role in User Management: Chronicle reports needs "Can see detailed user activity in Chronicle", Tool & category management needs "Can change tools and category of tools", and Billing & subscription is for the Owner and for Admins with "Can manage billing information". An Admin can set Time off to Write only with "Can approve time off for the people they manage". Organization settings and Destructive changes appear for the Owner and Admins only.
  • Managers' cards stop at Read. Their card says: "Your role connects read-only: the AI clients you connect cannot change anything."

Allowing Changes

  1. On the MCP access card, set a group to Write, either with Customize or with the Write preset. An Admin can do this only for groups the Owner has set to Write on the organization card.
  2. An Allow changes? dialog lists what connected AI clients will be able to change in each group, and marks the changes that also need Destructive changes. Click Allow to apply the selection to the card, or Cancel.
  3. Click Save. Nothing changes until you save.
  4. A Reconnect your AI clients to make changes notice appears. AI clients that were already connected keep read-only access until they are disconnected from Intelogos and connected again once. When a client reconnects, the approval screen asks to read and change Intelogos and says the client will make changes on your behalf; click Allow. Clients connected later need nothing extra.

How a Change Is Made

  • The assistant never changes anything in one step. It first proposes the change, and Intelogos returns a preview: what changes from what to what, and who or what is affected. The change is applied only after it is confirmed.
  • A confirmation is valid for 10 minutes and can be used once. If the assistant proposes the same change again later, that is a new change, and confirming it applies the change again. Read every preview, even one that looks familiar.
  • For a destructive change, the confirmation must repeat the preview's title exactly.
  • The assistant acts as you. Intelogos checks your role and permissions when the change is proposed and again when it is confirmed, and refuses anything you couldn't do in Intelogos yourself.

Keep your AI client's approval prompts on. The confirmation is sent by your AI client, so Intelogos can't tell whether a person approved it. Leave your client's own approval prompts switched on for the Intelogos tools, rather than allowing them always, so that you see and approve each change yourself.

Destructive Changes

Some changes are harder to undo than others: deleting projects and work policies, deactivating people, changing roles and permissions, editing many people at once, turning Projects off for everyone, and background-agent changes that affect your bill. These need Destructive changes set to Allow, on top of their own group being at Write. The switch starts at None. The changes that need it are marked in What Your Assistant Can Change.

What an Assistant Can Never Do

  • Change a person's role to Admin. Do this on the person's profile in Intelogos.
  • Delete a person permanently. The assistant can deactivate an account; deleting it is done in Intelogos.
  • Anything your own role and permissions don't allow. If you can't approve someone's time off in Intelogos, your assistant can't either.
  • Make changes from a Manager's connection. Managers connect read-only.

Turning Changes Off

  • Set the group back to Read or None, or set Destructive changes back to None, and click Save. This takes effect within seconds, and no reconnect is needed.
  • To cut a client off completely, deactivate or delete your credentials in Settings → MCP (see Managing Access). A client that is already connected can keep working for up to an hour, so lower the access level first if changes need to stop right away.

Change History

Intelogos records every change made through MCP: what changed, from what to what, and which account confirmed it. There's no screen for this record in the app; contact Intelogos support if you need to know what an assistant changed.


What Your Assistant Can Change

Every change needs its data group set to Write. Changes marked Destructive also need Destructive changes set to Allow. The same list appears under Can change when you expand a group on the MCP access card. Each change is previewed and applied only after it is confirmed (see How a Change Is Made).

Employee & Organization Directory

Owners and Admins.

  • Invite new people to the organization (up to 20 at a time)
  • Resend an invitation email
  • Change a person's first or last name
  • Change a person's job title or department
  • Change which projects a person belongs to
  • Make someone a regular user or a manager — Destructive
  • Change what a manager or admin is allowed to do — Destructive. Only the Owner can grant "Can manage billing information", and only to an Admin
  • Deactivate a person's account — Destructive
  • Change many people in one go (up to 50 people: job title, department or projects) — Destructive

Organization Settings

Owners and Admins.

  • Change the day the work week starts
  • Change the company-wide work-hours policy
  • Create a work-hours policy for some people, edit a policy or who it applies to
  • Delete a work-hours policy — Destructive
  • Change the short-day and long-day thresholds
  • Allow or block manual time edits
  • Create a project, rename a project or change its members
  • Delete a project — Destructive
  • Turn the Projects feature on or off for everyone (turning it off hides projects; nothing is deleted) — Destructive

Background Agents

Owners and Admins. Attaching, detaching or revoking a machine and resuming or blocking tracking change the number of background agents you are billed for. Resuming or blocking tracking and editing a background-agent person also need a plan that includes background agents.

  • Attach a background-agent machine to a person — Destructive
  • Detach a background-agent machine — Destructive
  • Revoke a background-agent machine (it has to register again) — Destructive
  • Make a machine the person's Host device
  • Resume or block background tracking for a person — Destructive
  • Edit a background-agent person's name, job title or department

Tool & Category Management

The Owner, and Admins with "Can change tools and category of tools".

  • Mark a tool primary, secondary, neutral or distracting
  • Remove an importance rule from a tool
  • Apply a department preset's importance list
  • Set or clear a tool's time category

Chronicle Reports

The Owner, and Admins with "Can see detailed user activity in Chronicle".

  • Change a project's auto-assign keywords

Time Off

An assigned approver of the request: the Owner, or an Admin with "Can approve time off for the people they manage". The Time off feature must be turned on.

  • Approve or decline a pending time-off request. An approval completes the request only when every assigned approver has approved it; a decline settles it at once.

Example Prompts

Try these first. The answers are illustrative and use fictional teams and numbers, not data from a real organization.

"Which departments had the lowest availability last week?" Example answer with sample data: Across 4 departments, Customer Support had the lowest availability at 81% of expected hours, followed by Design at 88%. Engineering and Sales were both above 92%.

"Summarize how the design team spent its time yesterday." Example answer with sample data: The 6-person Design team logged 41 active hours. 62% went to design tools, 21% to communication apps and 9% to browsers. Two people had more than 90 minutes of idle time in the afternoon.

"Who is on time off next week, and will any team be short-staffed?" Example answer with sample data: Three approved requests overlap next week: two in Sales (Monday to Wednesday) and one in Engineering (all week). Sales will be at 60% headcount on Monday and Tuesday.

"Show the top tools used by the Sales department this month and flag any distracting ones." Example answer with sample data: Top tools: the CRM (38% of active time), email (22%) and video calls (15%). Two tools are categorized as distracting: a video streaming site (2.1 hours in total) and a news site (1.4 hours).

"Compare this week's productivity KPI with last week for the whole organization." Example answer with sample data: Productivity is 84% this week, up 3 points from 81% last week. Activity is flat at 77%. The largest gain came from Engineering (up 6 points); Customer Support fell 2 points.

The next two make changes, so they need Tool & category management and Time off set to Write.

"Mark Figma as a primary tool for the Design department." Example answer with sample data: Here is the change: Figma for the Design department, from Neutral to Primary, affecting the 6 people in Design. Confirm and I'll apply it. After you confirm: Figma is Primary for Design.

"Approve Anna's vacation request for next week." Example answer with sample data: Anna asked for 5 days of vacation, Monday to Friday next week, and has 12 days left. Confirm and I'll approve the request.


Managing Access

Each person manages their own connection from Settings → MCP:

  • Generate credentials creates your Client ID and Client Secret.
  • Regenerate issues a new Client Secret, and the old secret stops working. Update every client that uses it.
  • Deactivate revokes access with your current credentials. Deactivated credentials can't be turned back on: to connect again, click Generate credentials to create new ones.
  • Delete removes your credentials permanently.
  • The MCP access card sets what your connected clients can read and change. See Letting Your Assistant Make Changes.