Organization & Access (read-only) — MCP Tools

Read-only members, teams, custom roles and effective permissions. This page documents the Organization & Access (read-only) group of the Routebase MCP server, with the scope and the parameters of each tool.

A session that stages its tools advertises this group once the agent calls enable_toolset with the slug identity. Full-access keys, scoped keys and OAuth sessions see every tool they are allowed to call without that step.

get_custom_role

Get one custom role by ID: its permission strings, how many members hold it and when it was last changed. Get the ID from list_custom_roles or from a member's customRoleId. Requires organization context. Read-only: members, roles, teams and SSO are not changeable through MCP by design — a human does those in the web app.

No special scope — available to any authenticated key.

Parameter	Type	Required	Description
roleId	string	Yes	Public ID (GUID) of the custom role

get_my_permissions

Get the caller's own role and effective permission strings in the active organization — custom roles resolved. This is the tool to reach for after a permission error: it says what the caller actually holds. Set includeCatalog to also get every permission the product defines with its description, to map a denied action onto a name. Requires organization context. Read-only: members, roles, teams and SSO are not changeable through MCP by design — a human does those in the web app.

No special scope — available to any authenticated key.

Parameter	Type	Required	Description
includeCatalog	boolean	No (default false)	Also return the full catalog of permissions the product defines (default false)

list_custom_roles

List the organization's custom roles with the permission strings each one grants and how many members hold it. Use this to browse custom roles; for one role with its permissions use get_custom_role. Requires organization context. Read-only: members, roles, teams and SSO are not changeable through MCP by design — a human does those in the web app.

No special scope — available to any authenticated key.

No parameters.

list_members

List the organization's members with their role, the custom role if they have one, when they joined and when they last logged in. Use this for the organization's members; for the teams they belong to use list_teams. Requires organization context. Read-only: members, roles, teams and SSO are not changeable through MCP by design — a human does those in the web app.

No special scope — available to any authenticated key.

No parameters.

list_project_teams

List the teams that reach the active project and with which role. The other direction of list_team_projects — this is the tool for 'who can write here'. Requires project context. Read-only: members, roles, teams and SSO are not changeable through MCP by design — a human does those in the web app.

No special scope — available to any authenticated key.

No parameters.

list_team_projects

List the projects a team is assigned to and with which role (read or write). Unlike list_teams this only needs organization membership. Requires organization context. Read-only: members, roles, teams and SSO are not changeable through MCP by design — a human does those in the web app.

No special scope — available to any authenticated key.

Parameter	Type	Required	Description
teamId	string	Yes	Public ID (GUID) of the team

list_teams

List the organization's teams with their member and project counts. Set includeMembers to also get who is in each team — that costs one query per team and is capped at the first 25. Use list_team_projects for which projects a team reaches. Requires organization context. Read-only: members, roles, teams and SSO are not changeable through MCP by design — a human does those in the web app.

Required scope: org:manage-teams

Parameter	Type	Required	Description
includeMembers	boolean	No (default false)	Also return the members of each team (default false, first 25 teams)