Skip to main content
Help Center

Available MCP tools

The base tools of the teamspace MCP by category – which exist, what they do and which belong in a tailored access.

teamspace’s MCP construction kit is made up of base tools. An administrator selects from them what an access should offer – see Select and tailor tools. This page lists what is on offer.

What you see here is not what you get. This list shows the catalogue. Which tools are available to you depends on how your access is tailored – and what you see with them depends solely on your permission profile. The quickest way is to ask your assistant itself: “Which tools do you have for teamspace?”

Categories

When adding a tool, you first choose the Category. It groups the tools by area:

CategoryExplanation in the dialog
Open itemsTools for managing open items
ProjectsTools for project management
AppointmentsTools for appointment management
Project timesTools for project time tracking
FilesTools for file management
SalesTools for sales management
AttendanceTools for attendance management
CapacityTools for capacity planning
ExpensesTools for expense management
PersonnelTools for personnel management
CRMTools for CRM management

Tools at a glance

The tools follow a consistent pattern that is easy to remember:

  • “Search …” returns a list of hits for a search term.
  • ”… information” returns the details of a single record.

In practice they almost always belong in an access as a pair: search first, then drill in.

General and context

ToolWhat it returns
Who am IThe logged-in user. Small but important – without this tool the assistant doesn’t understand questions like “my tickets” or “my team”.
AgendaThe user’s agenda.
Activities for the last monthWhat has happened over the past four weeks – useful for reviews and weekly reports.

Personnel

ToolWhat it returns
Search employeesA list of hits for employees.
Employee informationDetails of an employee.

CRM

ToolWhat it returns
Search contactsA list of hits for contacts.
Contact informationDetails of a contact.

Tickets

ToolWhat it returns
Search ticketsA list of hits for tickets.
Ticket informationDetails of a ticket.
Search ticket channelsA list of hits for ticket channels.
Ticket channel informationDetails of a ticket channel.
Search ticket processesA list of hits for ticket processes.
Ticket process informationDetails of a ticket process.
Search ticket statusesA list of hits for ticket statuses.
Ticket status informationDetails of a ticket status.

Why so many ticket tools? Because an assistant asked to “group all untouched bug tickets by status” needs first the channel, then the statuses and then the tickets. This fine breakdown is the reason it works without a ready-made report.

Projects

ToolWhat it returns
Search projectsA list of hits for projects.
Project informationDetails of a project.
Search project rolesA list of hits for project roles.
Project role informationDetails of a project role.

Files

ToolWhat it returns
Retrieve file detailsDetails of a file.

An example configuration

The “Employee” access with the description “For everyday tasks” reaches around 42k tokens with 36 active tools – “fits comfortably”, according to the details panel. It contains Agenda, Who am I, Activities, the employee and contact tools, the full ticket block, the project tools, Organisations and file details.

That covers the everyday work of most colleagues – and not a single personnel, finance or expense tool is included. That is exactly what good tailoring looks like.

Notes

  • The catalogue grows. This list reflects today’s state; new base tools are added continually. What counts is always the category dropdown in your tenant.
  • The label is adjustable. An administrator can give each tool a name of their own within their access; the base tool behind it stays the same.
  • Tools know no permissions. Whether a tool sits in the access says nothing about what you see with it – see Security and permissions with MCP.
  • More is not better. Every additional tool costs speed and accuracy – see How MCP works in teamspace.