MCP server technical documentation.
For IT, security and developers. How ALITEO connects to AI, what AI may do and how the administrator keeps it under control.
What the MCP server is
Model Context Protocol (MCP) is an open standard that lets AI assistants call the tools of external applications. The ALITEO MCP server is part of API V4. It offers the assistant a set of tools, such as “search tasks”, “create a timesheet” or “change the solver”, and the assistant decides which one to use.
The assistant receives tool descriptions and parameters directly from the server, so there is nothing else to configure. This page is for people: it shows how to connect ALITEO, what the assistant may do and how the company administrator keeps it under control.
MCP or REST API?
| MCP server | REST API V4 | |
|---|---|---|
| For whom | AI assistants and agents | Integrations, scripts, synchronisation |
| Who acts | The signed-in user (OAuth) or a company AI agent | The company via an API key |
| Permissions | The user’s rights, narrowed by the Read / Write / Admin level | According to the API key |
| Documentation | The server sends tool descriptions to the assistant; this page is for people | OpenAPI at /docs |
| Call limit | Shared company API limit (see Limits) | |
Connection
Server address
https://api.aliteo.com/mcp
The transport is Streamable HTTP (JSON-RPC over POST), sign-in uses OAuth 2.1. The client discovers everything it needs from standard metadata (/.well-known/oauth-protected-resource). The OAuth client ID is the same for everyone: 6b628c55-da54-4281-8cd7-14c8a1b063f7. You can also find both values in the application: click your name and open MCP connector.
The variant https://api.aliteo.com/mcp/{companyId} binds the connection to one company. The assistant then does not have to choose a company and the tools do not need it as an argument.
Before you start
- The company has a paid licence with API access. MCP is licensed together with the REST API.
- The company administrator has allowed the AI client (Claude, ChatGPT or a generic MCP client) in Company settings › Integration › MCP connector. Everything is turned off by default.
- You are an internal, active member of the company. External users cannot connect to MCP, even with a licence.
Steps
- In your AI client, add a new connector (custom connector / MCP server) and enter the server address. Enter
6b628c55-da54-4281-8cd7-14c8a1b063f7as the OAuth client ID. ALITEO does not support automatic client registration. - The client opens the ALITEO sign-in page. Sign in with your account.
- On the consent page, choose the permission level: Read, Read and write or Admin. The level applies to the whole connection. For a higher level, you need to connect again.
- Done. Ask the assistant, for example, “What open tasks do I have in ALITEO?”. If you are a member of several companies, the assistant asks which one to work in.
Generic MCP client (manual configuration)
Claude Code adds the server with a single command:
claude mcp add --transport http --scope user --client-id 6b628c55-da54-4281-8cd7-14c8a1b063f7 ALITEO https://api.aliteo.com/mcp
Clients configured with a file (Claude Code via .mcp.json, Cursor, VS Code and others) use this format:
{
"mcpServers": {
"aliteo": {
"type": "http",
"url": "https://api.aliteo.com/mcp",
"oauth": {
"clientId": "6b628c55-da54-4281-8cd7-14c8a1b063f7"
}
}
}
}
The exact configuration format differs between clients, follow your client’s documentation. The client must allow you to enter your own OAuth client ID.
Permissions
Three layers decide what the assistant may do. The strictest one always applies.
- The user’s rights in ALITEO. The assistant sees and changes only what the user can in the application. The same applies to membership in projects and teams, the administrator role and licences for paid features (SLA, branding).
- The level chosen when connecting. The user selects it on the consent page and can only narrow access with it.
- The company ceiling. The administrator sets the highest allowed level for the whole company and can grant exceptions to individual members or groups. A member exception applies first, otherwise the highest level of the member’s groups, otherwise the company ceiling.
Searching and reading data: tasks, projects, timesheets, meetings, users, settings.
In addition, creating and editing: tasks, comments, timesheets, projects, meetings, own settings.
In addition, company and workspace settings: users, groups, attributes, SLA, templates.
The assistant only sees the tools allowed by the connection level. At the Read level, the server does not offer write tools at all.
Security and audit
- Sign-in via OAuth. The assistant never sees the user’s password. The connection holds a token that can be revoked at any time.
- Sign-in overview. In Company settings › Integration › MCP connector, the administrator sees who connected and when, with which level, and which actions the assistant performed, including failed ones and the reason. The administrator can disconnect any connection for the company. Users see and disconnect their own connections in their personal settings.
- Irreversible actions are confirmed. Deleting settings (sections, phases, rules, SLA, templates…) takes two steps. The first call changes nothing and returns a confirmation card, only the second call with the confirmation token performs the action. The token is valid for 5 minutes and only for the same action.
- No duplicate writes. Every write tool requires an
idempotencyKey. If the assistant repeats a call after a network outage, the server returns the original result and does not write again (24 hours). - Changes are visible immediately. Whatever the assistant writes appears at once in the open application of other users, just like a change made in the UI.
- Data of one company only. Every call works within one company. The server rejects objects from another company.
Limits
| Limit | Applies to | Value |
|---|---|---|
| Company API limit | All tools working with a company. Shared with the REST API and all users of the company. | By licence, counted per minute |
| Per-user limit | Tools without a company (listCompanies, getConnectionInfo, getRateLimits) | 60 calls per minute per tool |
| Attachment uploaded via MCP (base64) | addTaskAttachment | Smaller files; the content passes through the model |
| Attachment via upload URL | createTaskAttachmentUpload | Up to 100 MB, URL valid for 15 minutes |
| Attachment download | getTaskAttachmentContent | Up to 10 MB, larger only in the browser |
| Search results | search* by name / filter | 100 / 10,000 records |
When the limit is exceeded, the tool returns the rate_limit_exceeded error with information on when the counter resets. The assistant can check current limits with the getRateLimits tool, which does not consume the company limit.
Company AI agents
Besides personal connections, a company can create an AI agent. It is an internal member without sign-in, with its own rights and its own MCP server. It suits automations that run without a person (routines, scheduled jobs) or a shared connector for a whole team.
- The administrator creates the agent in Company settings › AI agents. ALITEO can call the agent via webhooks and the agent works in ALITEO via MCP.
- The agent’s server address is
https://api.aliteo.com/mcp-agents/{agentId}. The connection is always bound to one company and the tools have nocompanyargument. - Sign-in either with the agent’s secret key (for runs without a person) or via OAuth: the company administrator signs in and selects the agent. Two keys allow rotation without downtime.
- The agent sees only what it can access as a member. If the agent’s webhook sends events from places the agent cannot see, the application warns about a permission conflict.
Example prompts
Just write to the assistant in plain language. It picks the tools itself. Below each prompt are the tools it typically uses.
“Which of my tasks are overdue? Sort them by priority and suggest where to start.”
listReactTasks · searchTasks · getTask“Which tasks in the Web 2027 project are critical and why?”
searchProjects · searchTasks (withCriticality) · getTask“Log 3 hours for me yesterday on task #1234, customer consultation.”
getTaskByNumber · listSourcesForTimesheetAdd · createTimesheet“Create tasks from these meeting notes and assign solvers.”
searchUsers · createTask · modifyTaskSolvers“Prepare the agenda for Friday’s team meeting based on open points from last time.”
searchMeetings · getMeeting · addMeeting“How many hours did the Support team log last month, by project?”
searchTeams · searchTimesheetsTool catalogue
The complete list of tools as the server offers them to the assistant. The level shown for each tool is the minimum the connection needs. Individual actions may also require a role (project, workspace or company administrator).
Troubleshooting
| What happens | Why and what to do |
|---|---|
| The assistant sees no company | The company has no licence with API access, the administrator has not allowed the AI client, or you are not an internal active member. Check Company settings › Integration. |
| The assistant can only read | The Read level was chosen when connecting, or the company ceiling limits it. The connection level cannot be raised, connect the connector again with a higher level. |
| “Not found or no access” | The object does not exist, or the user has no access to it. The server deliberately does not distinguish between the two. |
rate_limit_exceeded | The company API limit (shared with the REST API) or the user limit is exhausted. The error says when to try again. |
| The assistant asks for confirmation | It is an irreversible action. Check what is to be deleted and confirm it to the assistant. |
| Contacting support | The assistant finds the connection ID with the getConnectionInfo tool. Include it in your support request. |
Catalogue generated from the tool registration in FunctionApi, release 26.1.3, 09.11.2026. Internal tools (API documentation, test data) are not included.
We will set the agent up for you.
Prefer not to set it up yourself? We review your processes, design the agent, build it and bring it into your team in ALITEO.