A Model Context Protocol (MCP) server that provides access to OPET fuel prices data through Claude AI.
If you already use Opet MCP, the opet mcp mcp server is the piece that lets your assistant work with it directly. A Model Context Protocol (MCP) server that provides access to OPET fuel prices data through Claude AI.
The server ships on PyPI as opet, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Prerequisites — The Prerequisites tool exposed by this serverSetup — 1. Clone the repository: bash git clone cd opet-mcpConfiguration is passed through the environment: OPET_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Before using this MCP server, you need to set up the OPET API server first.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Opet MCP's toolset — Prerequisites, Setup — is a fair guide to whether it matches your workflow. It is maintained by sinanerdinc; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Opet MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Setup | 1. Clone the repository: bash git clone <repository-url> cd opet-mcp |
{
"mcpServers": {
"opet": {
"command": "uvx",
"args": ["opet"],
"env": {
"OPET_API_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Before using this MCP server, you need to set up the OPET API server first.
| Variable | Description | Required |
|---|---|---|
| OPET_API_URL | Endpoint or connection string the server talks to. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.