Epinu MCP server
{
"mcpServers": {
"epinu": {
"type": "http",
"url": "https://api.epinu.ai/api/agent/mcp"
}
}
}{
"mcpServers": {
"epinu": {
"type": "http",
"url": "https://api.epinu.ai/api/agent/mcp"
}
}
}{
"mcpServers": {
"epinu": {
"type": "http",
"url": "https://api.epinu.ai/api/agent/mcp"
}
}
}{
"servers": {
"epinu": {
"type": "http",
"url": "https://api.epinu.ai/api/agent/mcp"
}
}
}{
"mcpServers": {
"epinu": {
"type": "http",
"url": "https://api.epinu.ai/api/agent/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.4
What it does
Epinu MCP exposes a hosted marketplace for real-world assets (agricultural and energy sectors) to AI agents via a Streamable HTTP endpoint. Agents can search and read public listings anonymously, and draft proposals for new listings or projects with a delegated token, where every write requires human approval before execution.
- Search public marketplace listings and projects in agro and energy sectors without authentication.
- Have an agent draft a marketplace listing proposal that a human then reviews and approves or rejects in the Epinu dashboard.
- Check the status of a pending proposal after an agent has submitted it, before human approval occurs.
Tools this server exposes
| Tool | Does |
|---|---|
| getting_started | Returns orientation information for agents connecting to the Epinu endpoint. |
| marketplace_listings_search | Searches public marketplace listings for real-world assets. |
| projects_search | Searches public projects on the Epinu platform. |
| search | General search across public Epinu data. |
| fetch | Fetches a specific public resource by identifier. |
| marketplace_listing_create | Creates a pending proposal for a new marketplace listing, requiring human approval before it goes live. |
| project_create | Creates a pending proposal for a new project, requiring human approval before it is written to the database. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.