Bike MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bike_list_documentsA | Lists all open documents in Bike. Returns a list of all currently open documents with their names and IDs. The active (front) document is marked with an asterisk (*). Bike must be running for this tool to work. Args: None Returns: List of documents, one per line (active marked with *):
Examples:
Errors:
|
| bike_get_document_outlineA | Retrieves the complete outline structure of the currently open Bike document. Returns a hierarchical tree of rows with their IDs, text content, and children. Bike must be running with a document open for this tool to work. Args:
Returns: Human-readable indented outline with IDs: Document Name (doc:root-id)
Examples:
Errors:
|
| bike_create_documentA | Creates a new document in Bike, optionally with an outline structure. Args:
Returns: Document info: "Untitled (doc:XXX)" Examples:
Errors:
|
| bike_create_rowsA | Creates one or more rows with optional nested structure. Args:
Returns: Confirmation: "Created N row(s)" Examples:
Errors:
|
| bike_group_rowsA | Groups multiple rows under a new or existing parent row. Two modes:
Use position ('first'/'last' for root, 'before'/'after' with reference_id) to override placement. |
| bike_update_rowA | Updates one or more rows' text content and/or type. Args:
Returns: Confirmation: "Updated N row(s)" Examples:
Errors:
|
| bike_delete_rowA | Deletes one or more rows from the document. WARNING: This is a destructive operation. Deleted rows and all their children will be permanently removed. This action cannot be undone via the MCP server (though Bike's undo may work if used immediately). Args:
Returns: Confirmation with count: "Deleted 3 row(s)" Examples:
Errors:
|
| bike_query_rowsA | Search for rows using Bike's outline path syntax. Outline paths are powerful queries for filtering rows:
Args:
Returns: Matching rows formatted as:
Or scalar result (count, boolean, text) depending on the query. Examples:
Errors:
|
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 8 tools
Each tool targets a distinct operation: listing documents, retrieving outlines, creating documents, creating rows, grouping rows, updating rows, deleting rows, and querying. Even though create_document and create_rows both create structure, they operate at different levels (document vs. rows within a document), avoiding ambiguity.
All tools follow the pattern 'bike_<verb>_<noun>' using imperative verbs (list, get, create, group, update, delete, query). The naming is uniform and predictable, with only minor plural/singular variation that does not hinder understanding.
With 8 tools, the server is well-scoped for a focused outlining application. Each tool addresses a core functionality without unnecessary bloat, and the count feels natural for the domain.
The tool set covers essential CRUD operations for rows (create, read via outline/query, update, delete) and document lifecycle (create, list). Missing operations like explicit row reordering or document closing are minor and can be worked around via existing tools, making the surface largely complete.