MCP tools
Account and projects
Six MCP tools that let a connected agent read your account, list and inspect projects, and create or delete them
Account and projects
The account and project tools let a connected agent check which Doxa account it is signed in to, find the projects it can use, read a project's details, and create or delete projects. Other MCP tools then work inside the projects you chose during OAuth sign-in. See Connect an AI Agent with MCP for setup.
Tools in this group
| Tool | What the agent can do | Scope needed |
|---|---|---|
get_account | Read the signed-in account, including the teams the user belongs to and the user's role in each team. | projects:read |
list_projects | List the projects the grant covers. Team projects appear with their team. | projects:read |
get_project | Read one project by ID. | projects:read |
list_github_repositories | List the GitHub repositories that are available to connect to a project. | projects:read |
create_project | Create a new project. | projects:write |
delete_project | Delete a project. | projects:write |
projects:write implies projects:read, so a grant with write access can also use the read tools. For what each scope allows across all tools, see MCP Scopes and Approval Requests.
Check which projects an agent can see
Start with a read-only request so you can confirm the connection works before the agent changes anything. Ask the agent:
List my Doxa projects.The agent calls list_projects. The result includes only the projects you selected on the consent page. If you chose all projects, it includes every project you own and every team project you can read.
Ask for account details when you need your team roles:
Show my Doxa account and the teams I belong to.The agent calls get_account, which returns your teams with your role in each one.
Project access depends on your team role
Team projects follow the role you hold in the team. Tools check your role before they run:
A team project you can read appears in
list_projectsand works withget_project.If your role does not allow an action, the tool reports the project as not found. A viewer's agent can read a team project, but a write to it returns "not found".
Project services still run against the project owner's account, so the agent acts on the owner's projects within the limits of your role.
For how roles work, see Teams, roles and invites.
Create a project from an agent
create_project needs the projects:write scope. If you want the project connected to a GitHub repository, have the agent list the available repositories first:
List the GitHub repositories I can use, then create a Doxa project for the docs repository.The agent calls list_github_repositories to find the repository, then calls create_project. To generate docs for the new project, use the Generation tools.
Note:
Repository choices come from your GitHub connection. If a repository does not appear in list_github_repositories, check that Doxa can access it from your GitHub account.
Delete a project
delete_project removes a project. It needs the projects:write scope, so an agent with read-only access cannot delete projects. Before you grant write access, decide whether the agent should delete projects at all. Some consequential actions also go through an approval step; see Approval requests.
Ask the agent to confirm the project before it deletes anything:
Get the project named "Acme Docs" and confirm its ID before deleting it.