MCP server¶
The Touch2build MCP server lets an AI assistant work with your projects. Ask it in plain words, and it reads your tasks, changes them and prepares reports for you:
- "Which high-priority tasks are still open on the Résidence Les Tilleuls project?"
- "Mark task 42 as resolved with the comment seal replaced."
- "Tag every open task mentioning the lift with Ascenseur."
- "Prepare the Word report of the plumbing tasks, grouped by drawing."
- "How do I upload a new version of a drawing without losing its tasks?"
MCP (Model Context Protocol) is the open standard assistants use to call outside tools. Any assistant that supports remote MCP servers can connect: Claude, ChatGPT, Le Chat by Mistral, Claude Code, Cursor and others.
In development
The MCP server is in development. You can already use it with your account, but its tools, their names and their answers may still change.
Your feedback helps us finish it: tell us at support@touch2build.com what you ask your assistant, and what it could not do.
Server address¶
Connect your assistant¶
The server uses the Streamable HTTP transport and signs you in with OAuth. You do not create a key or copy a token: the assistant opens the Touch2build sign-in page, you sign in and approve the access, and the assistant receives a token for the MCP server only.
- In your assistant, add a remote MCP server, often called a custom connector, with the address above.
- When the assistant asks, sign in to Touch2build with your usual account and approve the access.
- Ask a first question, such as "List my Touch2build projects".
In Settings › Connectors, click Add custom connector, give it a name (Touch2build) and paste https://mcp.touch2build.com/mcp.
In Settings › Connectors, turn on developer mode if needed, then create a connector with the address https://mcp.touch2build.com/mcp and OAuth authentication.
The exact menus change often from one assistant to the next: if they differ, look for MCP, connector or integration in its settings.
What the assistant can do¶
| Area | Tools | Changes data |
|---|---|---|
| Projects | list your projects, read a project | no |
| Tasks | list and search tasks (state, priority, assignee, tags, text), read a task, download its photos | no |
| Tasks | change the status (open, resolved, closed), assign, comment, add or remove tags | yes |
| Reports | list the Word templates of a project, start a Word report, follow it until its download link is ready | yes, creates a report |
| User guide | browse this guide and read its pages, to answer questions on how to use Touch2build | no |
Each tool tells the assistant whether it only reads or also changes data. Most assistants ask your approval before running a tool that changes something: read what it is about to do before you accept.
Creating tasks, drawings, members and forms is not available through the MCP server yet. For those, use the app or the API.
Your data, your permissions¶
The assistant acts as you. It reaches only the projects you can open in the app, with the same permissions and the same licence: what the app refuses, the MCP server refuses too. Changes it makes appear in the history of the task under your name.
The token the assistant receives works only on the MCP server, not on the API or in the app. To cut the access, remove the connector in your assistant.
What you ask and what the tools return go through your assistant, under its own terms. Check them before you connect project data you must keep confidential.