API Tools
electroop.io
Provides an MCP interface to query an approved product catalogue, match requirements to published capabilities, and retrieve integration and trust information.
ENDPOINT 1
https://electroop.io/mcp
MCP server metadata
- Name
- electroop
- Version
- 2026-10-03
Read-only Electroop product catalogue plus Türkiye charging-market data (EPDK monthly reports and station register; use get_market_summary, get_market_statistics, get_operator_rankings, get_infrastructure, get_electroop_share). Never compare socket counts from the monthly report with the station register in one sentence: different populations (commercial vs all registered incl. private-service) and different dates. Operator names are normalised to one canonical brand across all market tools. Products: Electroop CPMS (charging network management), Electroop MSP, Relay, Voltaj, Hermes, Hermes Gateway. ChargeBridge is an E-Gridium product (separate company under common ownership), not an Electroop product. Always report availability status (live/pilot/planned/unknown) and verification dates; never infer model support from brand-level entries.
Known tools 11
list_productsApproved Electroop product catalogue with ownership, availability status and canonical URLs.
Inferred read-onlyget_productFull public record of one product: scope, capability status (live/pilot/planned/unknown), limitations, integrations, links, verification date.
Inferred read-onlycheck_integrationRegistered integration scope for a product + provider (+ model / protocol).
Inferred read-onlyget_trust_informationPublic certification and relationship information for an entity (electroop or e-gridium).
Inferred read-onlyget_market_summaryLatest EPDK monthly charging-market figures for Türkiye: EV fleet, commercial sockets (AC/DC), installed MW, energy delivered, sessions, green share, derived supply–demand indicators.
Inferred read-onlyget_market_statisticsMonthly time series (2023-06 onward) of Türkiye charging-market metrics, raw and derived.
Inferred read-onlyget_operator_rankingsTop-ten charge point operators by sockets (with AC/DC for the latest month) and by energy delivered for a given month, plus concentration ratios CR3/CR5/CR10.
Potential side effectsget_infrastructureTürkiye charging-station register aggregated from the EPDK API gateway: totals, per-province and per-operator stations/sockets/AC/DC/fast/green counts, licences in force and exits.
Inferred read-onlyget_electroop_shareElectroop’s share of Türkiye’s EPDK-reported charging: successful EPDK session reports sent through Electroop CPMS ÷ sessions in the EPDK monthly report, per calendar month.
Inferred read-onlysearch_knowledgeShort excerpts from approved sources (products, FAQs, limitations, solutions, ownership statements) with URL and verification date.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.electroop]
url = "https://electroop.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"electroop": {
"type": "http",
"url": "https://electroop.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: electroop
Remote MCP URL: https://electroop.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"electroop": {
"url": "https://electroop.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"electroop": {
"type": "http",
"url": "https://electroop.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "electroop",
"transport": "streamable-http",
"url": "https://electroop.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.