Consuming¶
You are calling fastgeoapi rather than running it — from an application, a script, or an AI agent.
There are two ways in, and they are the same data. OGC API over HTTP, which any standards-aware client already speaks. And MCP, which presents the same collections as tools an agent can call, with authorization of its own.
-
Learning-oriented. Connect a client and call your first tool.
-
Task-oriented. Verifying what a server is really exposing.
-
Information-oriented. The OpenAPI document the demo serves, the interoperability notes for testing against a deployment, and the MCP specifications this implements.
-
Understanding-oriented. What the MCP server is, how it authorizes, and why it is built the way it is.
If you only speak OGC API¶
Nothing here is required. The server is a standard OGC API — Features implementation and behaves like one; point your client at the landing page and follow the links. The OpenAPI document describes everything it serves, including the security schemes, which is what tells your client how to authenticate. For a desktop client, Using fastgeoapi from QGIS walks through the token, the features and the vector tiles on the public demo.
If you are testing a deployment rather than using one — a conformance harness, a gateway, your own client — the interoperability notes collect what the server declares, where the declaration and the behaviour part company, and how each of the two surfaces expects to be authenticated.