Easy8

Easy8 टूल्स जैसे इश्यू और प्रोजेक्ट्स के साथ इंटरैक्ट करें।

दस्तावेज़

MCP server ¶

The Easy8 MCP server lets AI assistants such as Claude, ChatGPT, Microsoft Copilot Studio or Cursor work with your Easy8. A user connects the assistant once, signs in with their Easy8 account and then asks:

"What tasks are assigned to me this week?"
"Create a task in the Website project to update the pricing page and assign it to Jane."
"Log 2 hours on task 1234 for yesterday."
"Summarise the comments and attachments of task 1234."
"Which of my opportunities had no sales activity last month?"

The assistant acts as the signed-in user: it sees only what that user can see and changes only what that user may change. Tools lists everything it can do.

Set up ¶

An administrator does this once.

1. Turn on MCP ¶

In Administration → Settings → AI, check Enable MCP and save.

The server address is your Easy8 address followed by /mcp, for example https://yourcompany.easy8.com/mcp.

2. Choose how assistants sign in ¶

Method	Use it for	Where
Self-registration	Assistants that connect with the server address alone, such as Claude or Copilot Studio	Administration → Easy SSO → Apps using Easy8 accounts → Self-registration of applications
Manual application	Assistants that ask for a Client ID and secret	Administration → Easy SSO → Apps using Easy8 accounts → Add application
API key	Scripts and developer tools that send a header instead of signing in, such as Claude Code or Cursor	Each user's My profile → API access key; needs the REST API turned on in Administration → Settings → API

Self-registration has three modes:

Off (default): assistants cannot register themselves. Add each one as a manual application.
Approval required: a newly registered assistant waits for an administrator. Administrators receive an email, and the assistant appears under Waiting for approval with Approve and Reject.
Automatic: any assistant can register and sign people in right away. Use it only when you trust your network.

Manual application: click Add application, enter a name and the assistant's website and save. The application page shows the Client ID and Client secret to enter in the assistant.

With both methods, each user signs in to Easy8 and confirms access the first time they connect.

The Access policy of an application limits what it may do, on top of the user's permissions. Change it on the application page:

Access policy	Allows
All read/write, All read-only	MCP and REST API
MCP read/write, MCP read-only	MCP only
API read/write, API read-only	REST API only; MCP is refused

Connect an assistant ¶

Add Easy8 to the assistant as a remote MCP server with the address https://yourcompany.easy8.com/mcp. The assistant then opens the Easy8 sign-in page; sign in and click Authorize.

Claude (web and desktop): Settings → Connectors → Add custom connector. For a manual application, enter its Client ID and Client secret under Advanced settings.
Microsoft Copilot Studio: add the MCP server and choose OAuth 2.0 → Dynamic discovery. See Microsoft's documentation.
Claude Code: claude mcp add --transport http easy8 https://yourcompany.easy8.com/mcp, then sign in with /mcp. Signing in needs self-registration. Without it, use an API key: add --header "X-Easy8-API-Key: <your API key>".
Other assistants: tools that ask for a header instead of signing in accept the API key in the X-Easy8-API-Key header.

Security ¶

The assistant has the permissions of the signed-in user, never more.
A read-only access policy or the Readonly API access key from My profile lets the assistant read without changing anything.
No tool deletes tasks, projects, time entries or CRM records.
Changes are saved in the history under the name of the user who made them through the assistant.
For self-registered applications, to disconnect a user, open the application in Apps using Easy8 accounts and click Disconnect user. Switching the application off or deleting it disconnects everyone who uses it.
Turning off Enable MCP stops all MCP connections at once. Applications with an All access policy, the default, keep their REST API access until you switch them off. WebMCP has its own setting.
Descriptions and comments written by other people can contain instructions meant to mislead an assistant. Prefer assistants that ask before they change data.

Troubleshooting ¶

Problem	Check
The assistant cannot find the server (HTTP 404)	Enable MCP is on.
Connecting fails before the sign-in page appears	Self-registration is not Off, or add the assistant as a manual application.
The assistant says it is waiting for approval	An administrator approves it under Waiting for approval.
HTTP 401 with an API key	The key is correct and the REST API is turned on in Administration → Settings → API.
HTTP 403	The access policy of the application is API read/write or API read-only, which refuses MCP.
The assistant can read but not change data	The access policy or API key is read-only, or the user lacks the permission in Easy8.
Tools of a module, such as CRM, are missing	Your Easy8 does not include that module.
The assistant cannot open attachments	The assistant downloads files from Easy8 to analyse them. In Claude, turn on code execution and allow network access to your Easy8 address. A proxy login in front of Easy8 must let the assistant's download through.

Easy8 logs MCP requests in log/mcp.log, with the user, the tool and the reason a request was refused. A refusal by the access policy (HTTP 403) is only in log/production.log. On Docker, read the logs with docker compose exec app tail -f log/mcp.log.