Capacitor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPACITOR_MCP_URL | No | Set CAPACITOR_MCP_URL to point the proxy at a local server instead of the hosted one. | https://capacitor-mcp.capawesome.io/mcp |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Search the official Capacitor documentation from capacitorjs.com by keyword. Use this first for any question about Capacitor itself — the CLI, the |
| get_doc_pageA | Read the full markdown of a single page of the official Capacitor documentation. Use this after |
| list_pluginsA | List Capacitor plugins: the official plugins maintained by the Capacitor team and community plugins from the awesome-capacitorjs list maintained by Capawesome. Use this to find a plugin for a native capability before writing custom native code, and to learn which package name and maintainer a capability belongs to. Returns |
| list_blog_postsA | List the 10 most recent posts from the Capacitor tag of the official Ionic blog, newest first. Use this when the question is about what is new — recent releases, announcements or deprecations. The blog covers both Capacitor and Ionic Framework. Returns |
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 4 tools
Each tool targets a distinct job: blog feed vs. doc search vs. full-page retrieval vs. plugin discovery. The descriptions explicitly warn against using the wrong tool, so an agent should not confuse them.
All four tools follow a consistent snake_case verb_noun convention: list_blog_posts, search_docs, get_doc_page, list_plugins. The verb choices clearly signal the action each tool performs.
Four tools is well-scoped for a documentation-focused server: search, page retrieval, news, and plugin discovery each earn their place. It is neither bloated nor too thin.
The core documentation workflow is covered end to end: search, read a full page, list plugins, and check recent blog posts. Minor gaps exist—such as no way to fetch a full blog post or filter plugins—but they are workaroundable and the scope is clearly bounded.