FIWARE MCP Server

A First FIWARE Model Context Protocol Server

Local serverstdioPython

What is the FIWARE MCP server?

Most developer tooling work still happens through a UI a human drives. FIWARE MCP server moves it into the conversation instead. A First FIWARE Model Context Protocol Server.

The short version

This is a first implementation of a FIWARE Model Context Protocol (MCP) Server that provides a bridge between the Context Broker and other services. The server implements basic operations for interacting with a FIWARE Context Broker.

  • Context Broker version checking
  • Query capabilities for the Context Broker
  • Entity publishing and updating

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

The tools it exposes

The server publishes 2 tools. What each one is for:

  • Returns — JSON string with version information
  • Parameters — - address (default: "localhost")

What it needs from you

Configuration is passed through the environment: YOUR_AUTH_TOKEN, PUBLIC_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.

  • Python 3.7 or higher - pip (Python package installer) - Access to a FIWARE Context Broker instance

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. FIWARE's toolset — Returns, Parameters — is a fair guide to whether it matches your workflow. It is maintained by dncampo; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
ReturnsJSON string with version information
Parameters- address (default: "localhost")

How to install the FIWARE MCP server

{
  "mcpServers": {
    "CB-assistant": {
      "command": "uv",
      "args": [
        "run",
        "--with",
        "requests>=2.31.0",
        "--with",
        "fastmcp>=0.3.0",
        "python",
        "PATH\\TO\\FIWARE-MCP-Server\\server.py"
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Python 3.7 or higher - pip (Python package installer) - Access to a FIWARE Context Broker instance
VariableDescriptionRequired
YOUR_AUTH_TOKENCredential the server authenticates with.Yes
PUBLIC_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use FIWARE to Returns.
  • Use FIWARE to Parameters.

Frequently asked questions

Python 3.7 or higher, pip, and access to a FIWARE Context Broker instance. Required Python packages include `requests>=2.31.0` and `fastmcp>=0.3.0` (listed in `requirements.txt`).