Easy8

MCP Server

Easy8 provides a built-in MCP server on the /mcp endpoint.

The server exposes selected Easy8 functionality as MCP tools so that MCP-capable clients can discover tools, call them, and work with Easy8 issues, projects, users, time entries, and supported plugin data in a structured way.

What is MCP

MCP stands for Model Context Protocol.

In practice, it is a JSON-RPC based protocol that allows an AI client to:

• initialize a connection to a server

• discover available tools

• call those tools with structured arguments

• receive structured responses back

In Easy8, the MCP server is focused on project-management workflows. It lets an MCP client use Easy8 API capabilities through a tool catalog instead of hard-coding every REST endpoint.

Endpoint

Use the standard Easy8 application URL and append /mcp.

Example:

https://your-easy8.example.com/mcp

Discovery

Easy8 publishes an MCP Server Card for pre-connection discovery at:

https://your-easy8.example.com/.well-known/mcp/server-card.json

The card advertises the Streamable HTTP transport on /mcp, server metadata, current Easy8 brand icons, API key authentication, and the currently supported tool capability. It is public discovery metadata; the /mcp endpoint itself still follows the Enable MCP setting and API authentication rules.

MCP request and tool calls are logged to log/mcp.log with the effective user, method, tool name, selected request context, status, and duration.

How to enable the MCP server

The MCP server is disabled by default.

To enable it:

• Open Easy8 administration.

• Go to Settings.

• Open the AI tab.

• Enable Enable MCP.

• Save the settings.

When MCP is disabled, the /mcp endpoint returns 404 Not Found.

Documentation sections

• Authentication - API key usage, switch-user behavior, and how MCP resolves me.

• Protocol - supported MCP methods, HTTP behavior, and JSON-RPC examples.

• Core tools - built-in Easy8 tools for users, projects, issues, metadata, and time entries.

• Tool examples - prompt-to-tool examples and ready-to-use tools/call parameters.

• Plugin tools - tools contributed by optional plugins such as Helpdesk, Attendance, CRM, and Money.

• Extending tools - how plugins register MCP tools through EasyMcp::ToolRegistry.

• Security and troubleshooting - permissions, write-tool safety, errors, and common fixes.

Quick start

A typical MCP client flow is:

• Connect to /mcp with Easy8 API authentication.

• Call initialize.

• Call tools/list to discover the available tool catalog and schemas.

• Call a read tool, for example easy8_projects_list or easy8_issues_list, to resolve context.

• Call detail or write tools, for example easy8_issues_get, easy8_issues_create, or easy8_issues_update, if the API user has permission.