Connect an AI assistant
Visibr speaks the Model Context Protocol (MCP), an open standard that lets an AI assistant call the tools of another program. Through it an assistant can read a plan, try a what-if and make a change under the same rules as a person.
The address
An assistant connects to one address. It is also shown on the Connect screen of the app.
https://dev.visibr.com/mcp
- The transport is Streamable HTTP, without sessions: each request is a POST and each answer is one JSON response.
- The access token travels in the Authorization header, as a Bearer token.
- A token is accepted at this address only. It does not open the rest of the app.
Get a token
- Log in, open the menu under your name and choose “Connect AI”.
- Give the token a name, tick “Read-only” if the assistant should only look, and press “Create token”.
- Copy the token, or the ready-made set-up text under it. The token is shown this once.
Claude Code: run this once
claude mcp add --transport http visibr https://dev.visibr.com/mcp --header "Authorization: Bearer <your token>"
Other assistants: add this to their MCP settings
{
"mcpServers": {
"visibr": {
"type": "http",
"url": "https://dev.visibr.com/mcp",
"headers": {
"Authorization": "Bearer <your token>"
}
}
}
}
- A token belongs to one user and acts with that user’s role: owner, editor or viewer.
- Visibr stores only a SHA-256 hash of a token, so it cannot be shown again.
- A user can have 20 active tokens. Each can be revoked from the same screen, and a revoked token gives no access.
Read-only tokens
A read-only token in Visibr can call every tool that reads and both previews, which write nothing. It is refused every tool that writes, whatever the role of its user. A full token of a viewer cannot write either: a token never does more than its user may.
The tools
Visibr gives an assistant 20 tools. Each answers with structured data and the same data as JSON text.
| Tool | What it does | Changes anything |
|---|---|---|
list_plans | Lists every plan of the workspace with its three numbers, forecast finish, target and status. | No |
get_plan | Reads one plan in full: the figures, each piece of work with its dates, the people and the weeks. | No |
list_changes | Reads a plan’s change log, newest first: who, when, what, why, and the effect on the finish date. | No |
list_people | Lists the people of the workspace with their roles and the days a week they can work. | No |
get_people_load | Reads each person’s load for every week across all plans, with the weeks over 100% marked. | No |
preview_plan | Works out the finish date for scope and people that are not saved anywhere: a what-if for a new plan. | No |
preview_change | Shows what one change would do to a plan’s finish date, and whether it would need a reason. Saves nothing. | No |
create_plan | Creates a plan from a name, a target date, lines of scope and people. | Yes |
commit_change | Makes a change to a plan: scope, people, the target, the timesheet settings or the board’s columns. | Yes |
get_plan_page | Reads a plan as a page of text: one line per piece of work and per person, with a margin of computed dates. | No |
preview_plan_page | Shows what saving an edited page would change, line by line, and what it would do to the finish date. Saves nothing. | No |
apply_plan_page | Saves an edited page: every change it asks for goes into the change log, or none when one is refused. | Yes |
get_board | Reads the board: every plan’s work by status, or one plan’s own columns with their cards. | No |
move_item | Moves a piece of work to another column, named by the column or by what it counts as. | Yes |
assign_item | Assigns a piece of work to a person, or to nobody. On a committed plan this needs a reason. | Yes |
get_timesheet | Reads a plan’s timesheet for a month: totals, days, weeks, each person against their cap, and the entries. | No |
log_time | Logs time a person spent on a plan on one day, with a note and, when wanted, the piece of work. | Yes |
update_time_entry | Corrects a time entry: only the fields given are changed. | Yes |
delete_time_entry | Deletes a time entry. | Yes |
set_timesheet_highlights | Writes the highlights text of a month’s timesheet. | Yes |
Same rules, same log
A change an assistant makes in Visibr goes through the same change command as a change made on the screen: the same limits, the same reason on a committed plan, the same revision numbers. Its row in the revision table names the user followed by “(via AI assistant)”, so the log shows which changes an assistant made and for whom. A call a rule refuses comes back as an error the assistant can read, with the reason.
Logging the day
The Visibr tool log_time is made to be called every day. The date is today unless one is given, the person and the piece of work can be named instead of looked up, and a key makes a repeated call replace its own entry instead of adding a second one.
Arguments of a log_time call
{
"planId": "<plan id>",
"person": "Ana Costa",
"amount": 6,
"unit": "hours",
"note": "Contract tests for the orders API",
"item": "Build the API",
"key": "2026-11-13 ana"
}The plan must have its timesheet on, and the person must be allocated on it. Logging time on work that is still to do moves it to in progress.
Limits today
- Sign-in by OAuth is not available yet. The assistant must be able to send the token in a header.
- There is no event stream: the address answers POST only.
- A client must send the header Accept: application/json, text/event-stream.
- An argument a tool does not know is refused by name rather than ignored.
Questions about assistants
Can an AI assistant change a plan without anyone noticing?
No. A change an assistant makes in Visibr goes through the same change command as a person's: on a committed plan it needs a reason and takes the next revision number, and its row in the revision table names the user followed by "(via AI assistant)".
Which assistants can connect to Visibr?
Any MCP client that can reach Visibr over Streamable HTTP and send an access token as a Bearer header. Sign-in by OAuth is not available yet, so a client that can only connect that way cannot be used.