> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/maiagent-user-guide/en/org/developer.md).

# Developer Tools

Back-office tools for developers and system integrators — API key management, API call logs, OAuth applications, and the MaiAgent MCP that lets external AI tools such as Claude and Cursor operate the

When developers or system integrators connect to MaiAgent programmatically, they use the following back-office features:

| Tool                                                                                                      | Purpose                                                                                                                                                                         |
| --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [API Key Management](https://docs.maiagent.ai/maiagent-user-guide/en/org/developer/api-keys.md)           | Administrators issue, restrict, disable, and revoke API keys on behalf of members; members can also create keys themselves from the account page                                |
| [API Call Logs](https://docs.maiagent.ai/maiagent-user-guide/en/org/developer/api-logs.md)                | View records of all calls made to MaiAgent through the API, including request content, response results, and performance data, to troubleshoot integration issues               |
| [OAuth Applications](https://docs.maiagent.ai/maiagent-user-guide/en/org/developer/oauth-applications.md) | Let external applications such as MCP clients connect through OAuth authorization, so members don't need to paste API keys into configuration files                             |
| [MaiAgent MCP](https://docs.maiagent.ai/tech/mcp/maiagent-mcp)                                            | Let external AI tools such as Claude and Cursor operate the MaiAgent platform directly through MCP, for example creating Agents and managing knowledge bases (Technical Manual) |

## Integration Documentation <a href="#integration-docs" id="integration-docs"></a>

* [Technical Manual](https://docs.maiagent.ai/tech): API quick start, Web Chat embedding and SDK, MCP, AI Gateway, identity integration
* [API Documentation](https://docs.maiagent.ai/api): Complete API endpoint reference


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maiagent.ai/maiagent-user-guide/en/org/developer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
