Skip to content

feat: Smithery mcp installation#53

Open
jor2 wants to merge 3 commits intomainfrom
smithery-mcp-installation
Open

feat: Smithery mcp installation#53
jor2 wants to merge 3 commits intomainfrom
smithery-mcp-installation

Conversation

@jor2
Copy link
Copy Markdown
Member

@jor2 jor2 commented Nov 18, 2025

Description

VS Code install button

  • Add VS Code install button badge to README that uses the vscode:mcp/install URL scheme
  • Enables users to install tim-mcp directly from README with a single click
  • Works with VS Code 1.88.0+ with MCP extension installed
  • fixes Make it easier to install MCP #51 for streamlining MCP installation

Smithery.ai

Adds Smithery.ai as a unified installation method for tim-mcp, providing users with an additional way to discover, install,
and manage the MCP server alongside existing installation options.

  • smithery.yaml: New Smithery registry configuration file that defines the server metadata, runtime requirements,
    installation method, features, and supported clients
  • README.md:
    • Added Smithery installation section with CLI commands for different clients
    • Updated table of contents to include Smithery as an installation option
    • Documented the benefits of using Smithery (unified discovery, easy configuration, automatic environment variable setup)

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

Jordan-Williams2 added 2 commits November 18, 2025 12:35
- Add VS Code install button badge to README that uses the vscode:mcp/install URL scheme
- Enables users to install tim-mcp directly from README with a single click
- Works with VS Code 1.88.0+ with MCP extension installed
- Addresses issue #51 for streamlining MCP installation
The VS Code install button configures MCP for VS Code's native support only.
Add a note directing Claude Code CLI users to the separate claude mcp add command.
@jor2 jor2 self-assigned this Nov 18, 2025
- Create smithery.yaml configuration for Smithery registry listing
- Add Smithery CLI installation instructions to README
- Document unified MCP server discovery and management via Smithery
- Update table of contents to include Smithery installation method
- Include status note that tim-mcp registration with Smithery is pending
- Use correct Smithery CLI client identifiers (claude, vscode, cursor, etc.)

This enables users to discover and install tim-mcp through the central
Smithery registry once registration is complete, providing an alternative
to individual tool setup.
@jor2 jor2 force-pushed the smithery-mcp-installation branch from 4f37510 to 5606589 Compare November 18, 2025 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make it easier to install MCP

1 participant