Easy Labs MCP Server
co.itseasyPublished by itseasy.coOfficial publisherv0.5.0Updated Oct 26, 2026
Payments data, revenue workflows, and merchant-application guidance for AI agents, by Easy Labs.
Overview
Easy Labs MCP server giving AI assistants access to payments data, revenue workflows and merchant-application guidance, via a remote endpoint or local npm…
- What you can do
- Work with payments data and revenue workflows through Easy Labs.
- Get guidance on merchant applications.
- Run against sandbox, production or demo data depending on the configured environment.
- Explore deterministic sample data without an account by using the demo mode.
- When to use it
- Useful when an assistant needs to look at payment and revenue information or help with merchant onboarding questions through Easy Labs, and you want either a hosted endpoint or a local stdio server.
- Requirements
- An Easy API key supplied as EASY_API_KEY or the x-easy-api-key header (live keys hit production, test keys the sandbox). Alternatively set EASY_ENVIRONMENT=demo, or send the literal value 'demo' in the header, to use sample data without an account. EASY_ENVIRONMENT selects sandbox (default), production or demo. The npm package @easylabs/mcp-server runs locally over stdio; a remote endpoint is also available.
Installation
In SourceWeft
- Open Easy Labs MCP Server in the dashboard and add it to a workspace.
- Connect x-easy-api-key credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/co.itseasy%2Feasy-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"easy-labs": {
"type": "http",
"url": "https://mcp.itseasy.co/mcp",
"headers": {
"x-easy-api-key": "<YOUR_API_KEY>"
}
}
}
}Tools
0Version history
1- v0.5.0LatestSep 16, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.