Bridge2AI Standards Explorer MCP
A Model Context Protocol (MCP) server for the Bridge2AI Standards Explorer that provides tools to search and query standards data from the Synapse platform using SQL.
Overview
This MCP server provides programmatic access to the Bridge2AI Standards Explorer table (syn63096833) on Synapse, enabling LLM applications to query and retrieve standards information through the Synapse Table Query API. The server uses FastMCP and implements Synapse's async query pattern with automatic polling.
Features
- SQL-Based Table Queries: Execute SQL queries directly against the Bridge2AI Standards Explorer tables
- Text Search: Convenient search tool for finding text across multiple columns
- Async Job Handling: Automatically handles Synapse's async query pattern with polling
- Pagination Support: Control the number of results and offset for paginated queries
- Table Information: Get metadata about the Bridge2AI Standards Explorer tables and project
Tools
query_table
Execute SQL queries directly against the Bridge2AI Standards Explorer tables.
Parameters:
sql_query(str, required): SQL query string to execute (e.g.,"SELECT * FROM syn63096833 WHERE name LIKE '%FHIR%' LIMIT 10")max_wait_seconds(int, optional): Maximum time to wait for query results (default: 30)
Returns: A dictionary containing:
success: Boolean indicating if the query was successfulsql_query: The executed SQL queryrow_count: Number of rows returnedtotal_rows: Total number of matching rowscolumns: Array of column definitions with names and typesrows: Array of result rows with their data
Example queries:
-- Simple query
SELECT * FROM syn63096833 LIMIT 10
-- Search for FHIR standards
SELECT * FROM syn63096833 WHERE Standard LIKE '%FHIR%'
-- Search across multiple columns
SELECT id, Standard, ShortDescription
FROM syn63096833
WHERE ShortDescription LIKE '%metadata%'
LIMIT 5
-- Complex filtering with pagination
SELECT id, Standard, Category
FROM syn63096833
WHERE Standard LIKE '%format%'
AND Category IS NOT NULL
LIMIT 10 OFFSET 5
search_standards
Search for text within the Bridge2AI Standards Explorer table (convenience wrapper around query_table).
Parameters:
search_text(str, required): The text to search for (case-insensitive)columns_to_search(list[str], optional): List of column names to search (default:["Standard", "ShortDescription"])max_results(int, optional): Maximum number of results to return (default: 10)offset(int, optional): Number of results to skip for pagination (default: 0)
Returns: Same format as query_table, plus:
search_text: The original search textsearched_columns: List of columns that were searched
Example:
# Search in default columns (Standard, ShortDescription)
result = await client.call_tool(
"search_standards",
{"search_text": "FHIR", "max_results": 5}
)
# Search in custom columns
result = await client.call_tool(
"search_standards",
{
"search_text": "metadata",
"columns_to_search": ["ShortDescription", "LongDescription"],
"max_results": 10
}
)
get_standards_table_info
Get information about the Bridge2AI Standards Explorer table.
Returns: Dictionary with table and project information including:
table_id: Synapse ID of the tableproject_id: Synapse ID of the project- URLs to view the table and project on Synapse
Installation
# Using uv (recommended)
uv pip install -e .
# Or using pip
pip install -e .
Development Installation
For development with testing dependencies:
uv pip install -e ".[dev]"
Configuration
The server is configured to query:
- Table ID:
syn63096833(Bridge2AI Standards Explorer Table) - Project ID:
syn63096806(Bridge2AI Standards Explorer Project) - Base URL:
https://repo-prod.prod.sagebase.org - Authentication: Optional via
SYNAPSE_AUTH_TOKENenvironment variable (see below)
Authentication (Optional)
This MCP accesses public Synapse tables only, so no authentication should be necessary. If you still need it for some reason, do the following.
For authenticated access, set the SYNAPSE_AUTH_TOKEN environment variable:
export SYNAPSE_AUTH_TOKEN="your_synapse_personal_access_token"
To get a Synapse Personal Access Token:
- Log in to Synapse
- Go to Account Settings → Personal Access Tokens
- Create a new token with appropriate scopes (at minimum: view, download)
Usage
Running the Server
# Using uv (recommended)
uv run standards-explorer-mcp
# Or using the CLI entry point directly
standards-explorer-mcp
# Or using Python module
python -m standards_explorer_mcp
The server communicates via stdio using the MCP protocol and will wait for messages from an MCP client.
Using with an MCP Client
Example using the FastMCP client:
from fastmcp import Client
async with Client("standards-explorer-mcp") as client:
# Execute a SQL query
results = await client.call_tool(
name="query_table",
arguments={"sql_query": "SELECT * FROM syn63096833 WHERE Standard LIKE '%FHIR%' LIMIT 5"}
)
print(results.data)
# Search for text across columns
results = await client.call_tool(
name="search_standards",
arguments={"search_text": "metadata", "max_results": 5}
)
print(results.data)
# Get table information
info = await client.call_tool(name="get_standards_table_info")
print(info.data)
Example Client
A complete example client is available in tests/example_client.py:
uv run python tests/example_client.py
Testing
Run All Tests
# Run complete test suite
uv run pytest tests/ -v
# Run with coverage report
uv run pytest tests/ --cov=src/standards_explorer_mcp --cov-report=html
Note: Integration tests use FastMCP's in-memory transport, automatically starting and stopping the server - no manual server startup required!
Architecture
Implementation Approach
The server uses Synapse's Table Query API which provides table-specific SQL query capabilities:
Async Job Pattern:
- POST to
/entity/{id}/table/query/async/start→ returnsasyncToken - Poll GET to
/entity/{id}/table/query/async/get/{asyncToken}- Returns 202 ACCEPTED while processing
- Returns 200 OK with results when complete
- Automatic retry with 1-second intervals
- Configurable timeout (default 30 seconds)
Benefits:
- ✅ Table-specific queries (results only from syn63096833)
- ✅ Full SQL WHERE clause support
- ✅ LIKE operator for substring matching
- ✅ Flexible column selection
- ✅ Built-in pagination with LIMIT/OFFSET
- ✅ No cross-contamination from other Synapse entities
Code Structure
The implementation separates business logic from MCP decorators for testability:
# Implementation function (testable)
async def query_table_impl(sql_query: str, max_wait_seconds: int = 30) -> dict:
# Business logic here
...
# MCP Wrapper (thin layer)
@mcp.tool
async def query_table(sql_query: str, max_wait_seconds: int = 30) -> dict:
return await query_table_impl(sql_query, max_wait_seconds)
This design allows:
- Direct testing of business logic without mocking MCP framework
- Fast test execution
- Easy debugging
- Clear separation of concerns
Development
Project Structure
standards-explorer-mcp/
├── src/
│ └── standards_explorer_mcp/
│ ├── __init__.py
│ ├── __main__.py
│ └── main.py # Main server implementation
├── tests/
│ ├── conftest.py # Shared test fixtures
│ ├── test_api_endpoints.py # API layer tests
│ ├── test_tools.py # Business logic tests
│ ├── test_mcp_integration.py # Integration tests
│ └── example_client.py # Example usage
├── pyproject.toml # Project configuration
└── README.md
Dependencies
fastmcp>=2.12.5- MCP server frameworkhttpx>=0.27.0- Async HTTP client for API callspytest>=8.0.0- Testing framework (dev)pytest-asyncio>=0.23.0- Async test support (dev)
Resources
- Synapse REST API Documentation
- FastMCP Documentation
- Model Context Protocol Specification
- Bridge2AI Standards Explorer on Synapse
- Bridge2AI Standards Explorer Table
Troubleshooting
Server won't start
Make sure dependencies are installed:
uv pip install -e .
Query fails
- Check internet connectivity to
repo-prod.prod.sagebase.org - Verify SQL syntax is correct
- For private tables, ensure
SYNAPSE_AUTH_TOKENis set
Tests fail
- Ensure you have the dev dependencies:
uv pip install -e ".[dev]" - Check that you have network access to Synapse API
- Some tests may require authentication for full functionality
Authentication issues
- Verify your token is valid and hasn't expired
- Ensure the token has appropriate scopes (view, download)
- Check that the environment variable is exported correctly
Support
For questions about:
- FastMCP: https://discord.gg/uu8dJCgttd or https://github.com/jlowin/fastmcp
- Synapse API: https://help.synapse.org/
- MCP Protocol: https://github.com/modelcontextprotocol
Metadata
Release files for standards-explorer-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 | Provenance | |
|---|---|---|---|---|
| standards_explorer_mcp-0.1.0.tar.gz | 97.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| standards_explorer_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 112.2 kB
Release files / standards_explorer_mcp-0.1.0.tar.gz
| Download URL | standards_explorer_mcp-0.1.0.tar.gz |
|---|---|
| Size | 97.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc6f62d2f7d23dd011e17c7daf2168bed517fe93e8655a0d8d378026ac1153b2
|
|
BLAKE2b-256 checksum How to use checksums |
eed2ed232322abca52028e49b52ed83f8c71c5d23514eff2f136f025b9ac689b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Oct 24, 2025.
Transparency logRelease files / standards_explorer_mcp-0.1.0-py3-none-any.whl
| Download URL | standards_explorer_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
62edf220ee39d0b95a2a6ee730dafbcee7530e52b91cf6e70acb32592a075b6b
|
|
BLAKE2b-256 checksum How to use checksums |
41dc1d1f3f904fd3a5411e774ad9f4b975e4f257160935ae730da9563f71ab21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Oct 24, 2025.
Transparency logSecurity for standards-explorer-mcp 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for standards_explorer_mcp-0.1.0.tar.gz
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 Oct 24, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.