Skip to content

Create voxaphone.json - #1632

Closed
rajpoothannan760-collab wants to merge 1 commit into
modelcontextprotocol:mainfrom
rajpoothannan760-collab:main
Closed

Create voxaphone.json#1632
rajpoothannan760-collab wants to merge 1 commit into
modelcontextprotocol:mainfrom
rajpoothannan760-collab:main

Conversation

@rajpoothannan760-collab

Copy link
Copy Markdown

Add voxaphone.json server definition to register VoxaPhone under the official MCP servers index.

Motivation and Context

Registers VoxaPhone—a sub-800ms, zero-data-at-rest voice execution substrate and Model Context Protocol (MCP) server for autonomous telephony and real-time enterprise workflow automation. This allows clients and developers using the Model Context Protocol to discover and connect to VoxaPhone.

How Has This Been Tested?

  • Verified JSON schema alignment against schema.json.
  • Validated voxaphone-mcp local build, TypeScript compilation, and Stdio/Webhooks communication.

Breaking Changes

  • No breaking changes (new server entry added to data/servers/voxaphone.json).

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

Repository Link: https://github.com/rajpoothannan760-collab/VOXAphone
Vendor: Voxana AI

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

Hi @rajpoothannan760-collab 👋 — thanks for your interest in the MCP Registry!

It looks like this PR is trying to publish an MCP server by adding or editing server files in this repository (under servers/, data/servers/, or in data/seed.json). That isn't how servers get published, so I'm closing this PR automatically.

Servers are published with the mcp-publisher CLI, not by opening a pull request against this repo. The CLI verifies that you own your namespace and submits your server.json directly to the live registry API.

To publish your server, follow the Publishing Quickstart. In short:

# Build the publisher CLI
make publisher

# Authenticate (e.g. via GitHub) and publish your server.json
./bin/mcp-publisher login github
./bin/mcp-publisher publish

Note: data/seed.json is seed data for local development only — adding entries there does not publish anything to the registry.

If you believe this was closed in error, please leave a comment and a maintainer will take a look. 🙇

This is an automated message.

@github-actions github-actions Bot added the invalid This doesn't seem right label Sep 9, 2026
@github-actions github-actions Bot closed this Sep 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

invalid This doesn't seem right

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant