Space Frontiers
Interfaces with the Space Frontiers API, enabling language models to interact with its data sources.
Space Frontiers MCP Server
General Overview
This project implements a Model Context Protocol (MCP) server that acts as an interface to the Space Frontiers API. It allows language models to interact with Space Frontiers data sources through MCP tools. The server is built using the FastMCP library.
The server provides 4 core tools for LLM-accessible search and discovery across Space Frontiers sources:
- search - Perform semantic search across multiple sources (scholarly literature, Wikipedia, Telegram, Reddit, YouTube, etc.)
- resolve_id - Convert document identifiers (DOIs, ISBNs, PubMed IDs, URLs, etc.) into standardized URIs with source information
- get_document - Retrieve a single document by URI with content filtering via search query (always returns filtered snippets)
- get_document_metadata - Fast retrieval of document metadata only (title, authors, abstract, references) without content search
Recommended Usage Pattern
The typical workflow for using these tools follows this pattern:
- search - Find relevant documents using a search query. This returns document IDs and snippets.
- resolve_id - If you have a document identifier (DOI, ISBN, URL, etc.), convert it to a URI and source name.
- get_document_metadata - Quickly get basic metadata (title, authors, abstract, references) without searching content. Fast and efficient.
- get_document - Retrieve filtered content from a specific document using its URI and a search query. Always returns only relevant snippets matching the query.
Example workflow:
User: "Find papers about CRISPR gene editing"
→ Use search("CRISPR gene editing") to get relevant papers
→ If a specific DOI is mentioned (e.g., "10.1038/nature12345"):
resolve_id("10.1038/nature12345")
Returns: {
"success": true,
"matches": [{
"resolved_uri": "doi://10.1038/nature12345",
"source": "library",
...
}]
}
→ Get metadata only (fast, no content search):
get_document_metadata(
document_uri="doi://10.1038/nature12345",
source="library"
)
Returns: title, authors, abstract, references
→ Get filtered content from the document (query is required):
get_document(
document_uri="doi://10.1038/nature12345",
source="library",
query="off-target effects"
)
Returns only the snippets relevant to "off-target effects"
→ For broader content, use a more general query:
get_document(
document_uri="doi://10.1038/nature12345",
source="library",
query="CRISPR methods results"
)
Returns snippets about methods and results
Tools are self-describing via MCP schemas and annotations; your MCP client can list and introspect them at runtime.
Hosted option: Space Frontiers provides a publicly hosted MCP server at https://mcp.spacefrontiers.org. Obtain an API key from https://spacefrontiers.org/developers/keys and include it via the Authorization: Bearer <your_api_key> header.
Environment Variables
The server utilizes the following environment variables:
SPACE_FRONTIERS_API_ENDPOINT: The base URL for the Space Frontiers API.- Default:
https://api.spacefrontiers.org
- Default:
SPACE_FRONTIERS_API_KEY: An optional API key for authenticating requests to the Space Frontiers API.- Note: Authentication can also be provided via request headers:
Authorization: Bearer <your_api_key>X-Api-Key: <your_api_key>- Alternatively, a user ID can be provided via the
X-User-Idheader. If none of these are provided, the server will attempt to use theSPACE_FRONTIERS_API_KEYenvironment variable if set. - Note on
X-User-Id: This header is intended for Space Frontiers internal usage only and cannot be exploited for external authentication.
- Note: Authentication can also be provided via request headers:
WIDE_MODE_LIMIT: Maximum number of snippets to return in "wide" mode forget_documenttool.- Default:
20
- Default:
FOCUSED_MODE_LIMIT: Maximum number of snippets to return in "focused" mode forget_documenttool.- Default:
5
- Default:
Running the Server
uv run fastmcp run mcp_server.py
Ensure SPACE_FRONTIERS_API_KEY is set in the environment if your client does not pass authentication headers.
Example Claude Desktop App Configuration (claude_desktop_config.json)
{
"mcpServers": {
"Space Frontiers MCP server": {
"command": "/path/to/your/uv",
"args": [
"run",
"fastmcp",
"run",
"--with",
"izihawa-loglib",
"--with",
"mcp[cli]",
"--with",
"spacefrontiers-clients",
"/path/to/your/spacefrontiers-mcp/mcp_server.py"
],
"env": {
"SPACE_FRONTIERS_API_KEY": "YOUR_API_KEY_HERE",
"WIDE_MODE_LIMIT": "20",
"FOCUSED_MODE_LIMIT": "5"
}
}
}
}
Note: replace placeholder paths and the API key with your actual values.
Related Servers
StreamNative MCP Server
Integrate AI agents with StreamNative Cloud resources and Apache Kafka/Pulsar messaging systems.
Autodesk Platform Services
An experimental MCP server providing access to the Autodesk Platform Services (APS) API.
Google Cloud Run
Official MCP Server to deploy to Google Cloud Run.
Alpaca MCP Server
Interact with Alpaca's Trading API for stock trading, portfolio management, and real-time market data.
Remote MCP Server on Cloudflare
A remote MCP server deployable on Cloudflare Workers with OAuth login support, using Cloudflare KV for data storage.
AWS MCP Server
Execute AWS CLI commands through the Model Context Protocol (MCP). Requires AWS credentials configured on the host.
Binance MCP Server
Access the Binance Futures API for trading, account management, and market data.
Claude Desktop
An MCP server for managing Kubernetes clusters, configured via an external JSON file.
Workers MCP
An MCP transport for interacting with your own Cloudflare Worker.
Hostinger
Official Hostinger API MCP server for services managment.