Updated
API and MCP reference
The CISO360AI REST API and MCP server: where their live schemas are published, and how to call them with an API key.
| You want to | Use | Where |
|---|---|---|
| Connect an MCP client | The MCP server | https://api.ciso360.ai/mcp |
| Get a machine-readable overview | The published llms.txt | api.ciso360.ai/llms.txt |
| Read the REST schema | OpenAPI schema, sent with your API key | https://api.ciso360.ai/api/openapi.json |
How the MCP server is shaped
The main tools are below; the server's tools/list method is the live list. Everything else is a capability reached through them.
| Tool | What it does |
|---|---|
list_projects | Lists the projects you can reach, each with its organisation; read it before choosing a project_id |
search_capabilities | Finds what the platform can do, by area or matching a query |
describe_capability | One capability's arguments, whether it reads or writes, and its response |
read_data | Runs a capability that reads. Without project_id it covers every project you can see |
change_data | Runs a capability that changes data. project_id is required; some capabilities file a proposal instead of making the change, and say so |
Two capabilities serve your own account: get_plan_and_entitlements (what your plan allows and how much is used) and search_product_docs (this help centre).
To connect an agent, see Connect an agent.
Call the REST API with a key
- Create an API key.
- Send it as a bearer token:
Authorization: Bearer <your-api-key>. - Take paths from the OpenAPI schema, which needs the same header.