BioOntology MCP Server

Created By
Augmented-Naturea year ago
A production-ready Model Context Protocol (MCP) server that provides comprehensive access to the BioOntology API for searching, annotating, and exploring over 1,200 biological ontologies.
Overview

What is BioOntology MCP Server?

BioOntology MCP Server is a production-ready Model Context Protocol (MCP) server that provides comprehensive access to the BioOntology API for searching, annotating, and exploring over 1,200 biological ontologies.

How to use BioOntology MCP Server?

To use the server, clone or download it, install the dependencies, and run the server with your BioOntology API key configured as an environment variable.

Key features of BioOntology MCP Server?

  • Search across ontology terms with advanced filtering options.
  • Annotate text and identify relevant ontology terms.
  • Get detailed information about specific ontologies and classes.
  • Access usage statistics and quality metrics for ontologies.

Use cases of BioOntology MCP Server?

  1. Searching for specific biological terms and their definitions.
  2. Annotating research papers with relevant ontology terms.
  3. Analyzing text data for ontology recommendations.

FAQ from BioOntology MCP Server?

  • Can I use this server for all biological ontologies?

Yes! The server supports over 1,200 biological ontologies available in BioPortal.

  • Is there a cost to use the BioOntology MCP Server?

No, the server is free to use, but you need a BioOntology API key.

  • How do I get a BioOntology API key?

You can create an account at BioPortal and generate an API key from your account settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Augmented-Nature
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago