sailfishos-mcp
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 |
|---|---|
| sailfish_create_projectB | Bootstrap a new SailfishOS application project with correct structure, RPM spec, and QML scaffolding. |
| sailfish_buildC | Build a SailfishOS project using the sfdk CLI (Sailfish SDK). Produces an RPM package. |
| sailfish_cleanC | Run |
| sailfish_deployC | Deploy an already-built RPM to a connected device or emulator via sfdk. |
| sailfish_guidelinesB | Return curated SailfishOS UI/UX and technical guidelines for a given topic. |
| sailfish_pitfallsB | List common mistakes and anti-patterns for a specific SailfishOS development area. |
| sailfish_snippetB | Return a ready-to-use code snippet for a common SailfishOS pattern. |
| sailfish_add_featureA | Add a new feature (page, cover, service, D-Bus interface, etc.) to an existing SailfishOS project. |
| sailfish_add_chum_metadataA | Inject SailfishOS:Chum metadata into the RPM spec of an existing project. Reads the License field and app name from the spec, the repository URL and author name from git, and the icon URL from the local icons/ directory. All values can be overridden. The metadata block is appended as the last paragraph of %description, wrapped in %if 0%{?_chum} … %endif. |
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 9 tools
Each tool has a clearly distinct purpose: metadata injection, feature addition, building, cleaning, project creation, deployment, guidelines retrieval, pitfalls listing, and snippet provision. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent 'sailfish_verb_noun' pattern, using snake_case throughout. This uniformity enhances readability and predictability, with no deviations in naming style across the set.
With 9 tools, the server is well-scoped for SailfishOS development, covering key lifecycle stages from project creation to deployment, along with supportive utilities like guidelines and snippets. Each tool earns its place without bloat.
The toolset provides strong coverage of core development workflows, including project setup, building, and deployment. Minor gaps exist, such as the lack of tools for testing or debugging, but agents can likely work around these with existing tools.