# Core

> Core is a modern PSA for MSPs: ticketing, assets, client CRM, SLA tracking,
> time tracking, billing, customer portal, and a built-in Core AI assistant —
> one platform, no multi-year contracts.

Core is the product at [core-it.tools](https://core-it.tools/). This file points agents at
canonical pages and the permission-scoped MCP server for workspace data access.

## Product

- [Home](https://core-it.tools/): Product overview and positioning
- [Features](https://core-it.tools/features): Platform capability index
- [Pricing](https://core-it.tools/pricing): Plans and per-technician pricing
- [Integrations](https://core-it.tools/integrations): NinjaOne, Slack, Everhour, Asana, and more
- [Schedule a demo](https://core-it.tools/schedule-demo): Book a walkthrough
- [Contact](https://core-it.tools/contact): Sales and support contact

## Documentation

- [Docs home](https://core-it.tools/docs): Guides for staff and admins
- [Getting started](https://core-it.tools/docs/getting-started): Onboarding overview
- [Tickets](https://core-it.tools/docs/guides/tickets): Ticket workflows
- [Customer portal](https://core-it.tools/docs/guides/customer-portal): End-customer portal
- [AI assistant](https://core-it.tools/docs/guides/ai-assistant): Core AI in the product
- [MCP server guide](https://core-it.tools/docs/guides/mcp-server): Connect permission-scoped external agents

## Compare and company

- [Compare](https://core-it.tools/compare): How Core differs from legacy PSAs
- [About](https://core-it.tools/about): Built by Rooted Software
- [Privacy](https://core-it.tools/privacy) · [Terms](https://core-it.tools/terms)

## MCP server (permission-scoped agent access)

An MCP client can connect as a signed-in Core user and use only the tools and
records that user is authorized to access. Connections can be read-only or can
receive explicit read-and-write consent.

- Endpoint: [MCP Streamable HTTP](https://core-it.tools/api/mcp)
- Server card: [https://core-it.tools/.well-known/mcp/server-card.json](https://core-it.tools/.well-known/mcp/server-card.json)
- Manifest: [https://core-it.tools/.well-known/mcp](https://core-it.tools/.well-known/mcp)
- Docs: [MCP server guide](https://core-it.tools/docs/guides/mcp-server)

### Auth

Sign in with a normal Core account, choose a workspace, and approve either
read-only or read-and-write access. Clients discover the flow automatically:

1. Call the MCP endpoint and receive `401` with `WWW-Authenticate`.
2. Follow metadata at [https://core-it.tools/.well-known/oauth-protected-resource](https://core-it.tools/.well-known/oauth-protected-resource).
3. Complete Core’s OAuth 2.1 login, pick a workspace, and approve access.

Never paste tokens into chat. Revoke anytime in Core: Settings → Agents.

### Capabilities

The tool list is returned only after sign-in and is filtered by the connected
user's effective permissions. Writes require read-and-write consent, stable
idempotency keys, mutation auditing, and—where needed—a short-lived approval in
Core. Results and mutation scope are capped and tenant-scoped.

### Example agent prompt

Connect to the Core MCP server at https://core-it.tools/api/mcp. Use the server’s browser
login/approval flow; do not ask me to paste tokens into chat.