Skip to content

Publish MCP Server as a standalone package #2421

@dwhoban

Description

@dwhoban

Problem

Currently the MCP server is not published to NPM.

For users to include it within other development tools they have to pull down the repository and run via a local command, which is not an ideal workflow.

This limits discoverability, and the ability to develop plugins and extensions for other MCP Marketplaces.

Solution

Update the deployment process to publish/release the MCP server under the existing @ansible/ansible-mcp-server package name and amend the documentation.

Guidance should also be given as to best practices for use of this server given the env context of a project workspace - i.e. should it be used as project level MCP server only.

Alternatives

The lightest alternative is to update the documentation to provide guidance on how to install and use the MCP server without VSCode - e.g. clone the repo.

The broadest alternative is to move this to a standalone repository but that seems unnecessary.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions