Skip to main content
Glama

capacitor-mcp

by io.capawesome
OverviewAdmin

List Capacitor plugins

list_plugins
Read-only

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 name, description, source, maintainer and url per plugin, plus core: true for a plugin that ships with @capacitor/core and experimental: true for an experimental one. Results are ranked by relevance, with official Capacitor plugins ranked first, then plugins maintained by Capawesome, then other community plugins. Do not use this to read a plugin's API: call get_doc_page with the url of an official plugin, and use the Capawesome MCP server at https://mcp.capawesome.io/mcp for Capawesome plugins.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoThe maximum number of items to return, e.g. 5. Defaults to 25, maximum 100.
queryNoA free-text filter matching the package name or the description, e.g. "camera". Defaults to no filter. Optional.
sourceNoWhich plugins to list: "official" for the plugins maintained by the Capacitor team, "community" for the awesome-capacitorjs entries, or "all" for both. Defaults to "all".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only and non-destructive hints; the description adds behavioral details such as result ranking and defaults, enhancing transparency without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and informative, though it slightly redundantly repeats the official/community distinction. Overall, it remains concise and each sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description fully explains the return fields (name, description, source, maintainer, url, core, experimental) and ranking behavior, providing complete context for a listing tool without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already provides full descriptions for all three parameters including enums and defaults. The description adds no significant extra semantic meaning beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists Capacitor plugins, distinguishes official and community sources, and explicitly names the sibling tool get_doc_page for reading APIs, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use the tool ('find a plugin for a native capability before writing custom native code') and when not to use it, directing to get_doc_page and the Capawesome MCP server, providing clear usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All capacitor-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources