Lacuna Research MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LACUNA_SITE_URL | No | Base URL of the Lacuna instance. | https://lacuna.tiptreesystems.com |
| LACUNA_MCP_TIMEOUT | No | Timeout in seconds for API requests. | 30 |
| LACUNA_MCP_LOG_LEVEL | No | Log level (DEBUG, INFO, WARNING, ERROR, CRITICAL). | WARNING |
| LACUNA_MCP_USER_AGENT | No | User-Agent header to use. | lacuna-research-mcp/{package_version} |
| LACUNA_MCP_MAX_RETRIES | No | Maximum number of retries for failed requests. | 2 |
| LACUNA_MCP_BEARER_TOKEN | No | Optional bearer token for private Lacuna deployments. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_lacunaA | Search Lacuna's ML/AI corpus for papers, research directions, authors, venues, institutions, novel research hypotheses, and research resources (code repositories, datasets, models, and demos linked to papers). For novel ML/AI research ideas, use search_type="hypothesis", then get_hypothesis on promising results. search_type accepts all, cluster, paper, author, institution, venue, hypothesis, or resource. Use paper for literature and get_paper to read a result. Use other sources for biographies, news, and non-research web content. Resources: search_type="resource" searches GitHub repositories, Hugging
Face datasets/models, and Zenodo records that Lacuna has linked to at least
one paper. To find benchmark or evaluation datasets, use
search_type="resource" with resource_kind="dataset" (for example query
"image classification benchmark" or a dataset name like "ImageNet").
resource_kind accepts codebase, dataset, model, or demo (one value or a
list); provider accepts github, huggingface, or zenodo. Both filters require
search_type "resource" or "all" (with either filter set, only resources are
returned). Each result has an external ranking_profile accepts:
sort accepts relevance (default), year_desc, or year_asc. Semantic ranking cannot use year sorting; constrain recency with date_from/date_to instead. date_from and date_to are inclusive YYYY, YYYY-MM, or YYYY-MM-DD bounds. author_id_or_url constrains a paper search to one author. Pass an author ID or Lacuna author page URL; it requires search_type="paper". fields optionally restricts and weights lexical fields, for example "title^4,abstract". Supported names are title, abstract, summary, concepts, name, top_names, and venue, plus description, topics, provider_key, and paper_titles for resources (a resource's title already includes its description, topics, README text, and linked paper titles). Fields must exist on the selected search_type, weights must be within 0 < weight <= 100, and fields cannot be combined with semantic ranking. |
| get_hypothesisA | Fetch a generated novel ML/AI research proposal from Lacuna. Use after search_lacuna(search_type="hypothesis") to inspect a proposal. view selects the response shape:
|
| get_directionA | Fetch a Lacuna research direction/cluster. Use a numeric cluster ID (for example 25005) or a direction URL ending in that number. view selects the response shape (
|
| get_direction_papersA | Fetch paginated papers associated with a Lacuna research direction/cluster. view selects the per-paper shape:
|
| get_paperA | Fetch a Lacuna paper by artifact id or paper URL. include_resources adds linked resources (code repositories, datasets, models, and demos) in context and full views by default. Pass False to omit them; other views ignore this option. Pass a resource entry's id to get_resource for further details. view selects the response shape.
figure_limit (context view only) caps the figure preview (server default 3).
Pass 0 to suppress figure previews while keeping a |
| get_resourceA | Fetch a Lacuna research resource (code repository, dataset, model, or demo). Accepts a resource artifact ID (art_...) or a Lacuna resource URL containing that ID (/resource//art_...). The response includes the external url, a summary, facets (tasks, modalities,
size, license, access), provider metrics, a README/card excerpt,
|
| get_author_papersA | Fetch one page of an author's papers, ordered from newest to oldest. |
| get_author_directionsA | Fetch one page of an author's named research directions. |
| get_author_contextA | Fetch agent-oriented context for a Lacuna author. Author profiles describe research output (papers, directions, impact). A
free-text view selects the response shape:
Set include_neighbors=True to include similar authors as named, linkable records. Neighbor computation may add significant server latency. |
| get_author_neighborsA | Fetch one ranked page of neighboring/similar Lacuna authors. |
| get_venue_contextA | Fetch agent-oriented context for a Lacuna venue, optionally scoped to a year. Venue keys are opaque hashes (e.g. "d7bf22905bd6"), never human-readable names like "icml". Find the key first via search_lacuna(search_type="venue") or pass a /venue/... page URL. view selects the response shape:
|
| get_institution_contextA | Fetch agent-oriented context for a Lacuna institution. view selects the response shape:
Use get_institution_authors to page through the complete author list. |
| get_institution_authorsA | Fetch one page of authors affiliated with a Lacuna institution. Results are ordered by paper count. Use authors_total, authors_returned, authors_offset, and authors_truncated to page through the complete list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools target clearly distinct entity+facet combinations, and descriptions explicitly distinguish context views from dedicated paginated fetches. However, get_author_context's include_neighbors option overlaps with get_author_neighbors, and context views include capped papers/authors that dedicated tools like get_author_papers and get_direction_papers also provide, creating minor boundary blur.
All tools follow a consistent snake_case verb_noun pattern: search_lacuna for search, and get_<entity>_<facet> or get_<entity>_context for fetches. There is no mixing of camelCase, different verb styles, or irregular naming.
13 tools map cleanly to the seven main entity types (paper, author, direction, venue, institution, resource, hypothesis) plus pagination and search needs. The set is neither bloated nor thin for a read-only research corpus.
Search covers all entity types, and dedicated fetch tools exist for papers, directions, authors, venues, institutions, resources, and hypotheses, with pagination where needed. Minor gaps remain, such as no non-context get_author or get_venue, no batch paper retrieval, but agents can work around these via search and context tools.