BOE-MCP. MCP Integration with the BOE API
DESCRIPTION
BOE is the Official State Gazette of Spain.
Boe-mcp enables querying consolidated legislation, BOE/BORME summaries, and legal reference data directly through Claude AI and other MCP-compatible clients using the Model Context Protocol (MCP).
Boe-mcp is an MCP server that exposes tools for LLMs to access:
- Consolidated legislation of the Spanish legal system
- Daily BOE and BORME summaries
- Auxiliary tables for legal domains, jurisdictions, and government departments
KEY FEATURES
- Advanced search of consolidated legislation with date, jurisdiction, and validity filters
- Full legal text retrieval in XML/JSON formats
- Historical BOE and BORME summary queries
- Access to legal reference tables (domains, departments, legal relationships)
- Block-level navigation of legal texts
- Automatic consolidation status validation
INSTALLATION
Install with uv
Prerequisites
- Python 3.10 or higher.
- uv package manager.
Installing uv
The first step is to install uv, a package manager for Python.
It can be installed from the command line.
On macOS and Linux:
curl -LsSf https://astral.sh/uv/install.sh | sh
On Windows:
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
You can also install it with pip:
pip install uv
For more information about installing uv, visit the uv documentation.
INTEGRATION WITH CLIENTS LIKE CLAUDE FOR DESKTOP
- Go to Claude > Settings > Developer > Edit Config >
claude_desktop_config.json. - Add this configuration block under
"mcpServers":
"boe_mcp": {
"command": "uvx",
"args": [
"boe_mcp"
]
}
- If you have other MCP servers configured, separate them with commas
,.
USAGE EXAMPLES
Once configured, you can make queries like:
- "List current state laws on data protection"
- "Show the BOE summary for June 14, 2024"
- "Display the BOE legal domains table"
Metadata
Release files for boe-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| boe_mcp-0.1.0.tar.gz | 7.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| boe_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.5 kB
Release files / boe_mcp-0.1.0.tar.gz
| Download URL | boe_mcp-0.1.0.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
97fd6196c529db7f19703f736fdb1193d1e74fb48db0d08514d29de99a25bc7d
|
|
BLAKE2b-256 checksum How to use checksums |
d78d2f66474c76599480df7bc70e6ce10a8cf050ca3fc4d8ab073cb9c9022d16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 15, 2025.
Transparency logRelease files / boe_mcp-0.1.0-py3-none-any.whl
| Download URL | boe_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
063e444fa99a6e31173358766ac24ada21dcef284e35306a9df357b45d54d4ef
|
|
BLAKE2b-256 checksum How to use checksums |
c8e203c5a86684b44eba69518795b8c610cb384563f54d24810bade5a85d6eed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 15, 2025.
Transparency log