Where it fits
French property developers and planners checking zoning rules before a site plan.
- Look up zoning rules for a French parcel.
- Get cited regulation pages for returned zoning values.
- Check parcel rules before preparing a site plan.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with PLU IA
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Hand the current conversation to a new background agent that picks up the work right away.
Turns a decision the user cannot fully answer into a questionnaire for someone else to fill in.
Covers writing documents for agents. Use it when creating or editing skills, or when modifying AGENTS.md or CLAUDE.md.
No skills found
Try a different search term or clear the filters.
Install it in your client
Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.
- 01
Run this command in your terminal
This adds PLU IA as a remote Streamable HTTP server in Claude Code.
Claude Codeclaude mcp add --transport http plu-ia https://pluia.fr/mcp --header "Authorization: Bearer pluia_YOUR_KEY" --scope project - 02
Send the credential
The provider expects the following header. Replace each placeholder with your own key or token before you connect.
Required headersAuthorization: Bearer pluia_YOUR_KEY - 03
Verify the connection
Run claude mcp list, or open /mcp in a Claude Code session.
Learn more about MCP in Claude Code
- 01
Run this command in your terminal
This adds PLU IA as a remote Streamable HTTP server in Codex.
Codex# Add this to Codex MCP settings: [mcp_servers."plu-ia"] url = "https://pluia.fr/mcp" [mcp_servers."plu-ia".headers] "Authorization" = "Bearer pluia_YOUR_KEY" - 02
Send the credential
The provider expects the following header. Replace each placeholder with your own key or token before you connect.
Required headersAuthorization: Bearer pluia_YOUR_KEY - 03
Verify the connection
Run codex mcp list, or open /mcp in a Codex session.
Learn more about MCP in Codex
- 01
Install with one click
This opens Cursor with the server pre-filled. Review the connection before accepting it.
Install in Cursor - 02
Send the credential
The provider expects the following header. Replace each placeholder with your own key or token before you connect.
Required headersAuthorization: Bearer pluia_YOUR_KEY - 03
Verify the connection
Open Cursor's MCP settings and enable the server if it is not active.
Learn more about MCP in Cursor
- 01
Install with one click
This opens VS Code with the server pre-filled. Review the connection before accepting it.
Install in VS Code - 02
Send the credential
The provider expects the following header. Replace each placeholder with your own key or token before you connect.
Required headersAuthorization: Bearer pluia_YOUR_KEY - 03
Verify the connection
Run MCP: List Servers from the Command Palette and start the server.
Learn more about MCP in VS Code
More clients, including project and global config files, are in the sidebar.
Endpoint and configuration
The installer uses the server name plu-ia. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
plu-iaappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Look up zoning rules for a French parcel. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
- The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
PLU IA documentationhttps://pluia.fr/api/v1/docs