Skip to main content

Submit a missing MCP server

Found an MCP server that is missing from LightNow and maintained by someone else? Send us its public repository URL. LightNow takes care of adding every supported MCP server it finds to the Registry.

One repository. One Registry entry.From public repository to versioned MCP server.
Public repositoryGitHub, GitLab, or Bitbucket
github.com/acme/mcp-server
Definition discoveryThe first valid match wins
server.json
manifest.json
mcp.json
pyproject.toml
package.json
Package syncPublish gate
Published in the RegistryVersioned and discoverable
acme/mcp-server

Submit from the Registry​

If someone else's public MCP server is missing from the Registry, paste its repository URL and LightNow takes care of the rest.

  1. Sign in to LightNow.
  2. Open Create → Submit repository.
  3. Enter the public repository URL and select Submit.
  4. Follow the status on the page, or return later to Recent submissions.
  5. When processing is complete, open the published MCP server from the result.

Processing can take several minutes and continues after you leave the page. Submitting a repository adds supported MCP servers to the Registry; it does not install them.

LightNow repository submission page with a repository URL field and recent submissions
Submit the repository once. Progress and previous submissions remain available on the same page.

Use this path when an imported or manually added server appears as Custom in a Runtime Profile. Linking replaces the Custom identity with the versioned Registry identity while keeping the instance runnable.

  1. Open Profiles and select the Runtime Profile that contains the Custom server.
  2. Select the server and open Link.
  3. Search the Registry first. If the MCP server already exists, select it and link immediately.
  4. If it is missing, select Import from repository, enter its public repository URL, and submit it.
  5. Close the dialog if you want. Processing continues, and the active request is shown when you return to the server.
One resultLinked automatically

When the repository produces one MCP server, LightNow links it to the selected Custom instance as soon as publishing finishes.

Several resultsYou choose the MCP server

When several MCP servers are published, select the one that belongs to the Custom instance. Other artifact types cannot replace it.

No runnable resultThe Custom server remains

A failed submission or link does not silently remove the existing server. The displayed status explains why the repository was not published.

What linking keeps​

LightNow carries the instance-specific settings to the selected Registry version:

  • the instance alias in the Runtime Profile;
  • command, arguments, transport, URL, headers, environment mapping, and other launch settings;
  • encrypted secrets managed by LightNow.

After linking, LightNow reloads the Runtime Profile and shows the regular versioned config and secret controls immediately.

Follow progress​

ProcessingLightNow is checking the repository

You can leave the page or close the Link dialog. Return through Recent submissions or reopen the Custom server.

PublishedThe MCP server is in the Registry

Review its repository, name, version, packages, transports, ownership, and trust signals before using it.

Selection requiredPick the matching MCP server

The repository produced several MCP servers. Select the result intended for this Runtime Profile instance.

Not publishedReview the result

The status explains why the repository was not published. Existing Custom config stays available.

Repository submission requires Registry write permission in the active Personal or organization context. Linking also requires permission to manage the selected Runtime Profile.