Meta Muse MCP Server by useapi.net (third-party)

net.useapiPublished by useapi.netOfficial publisherv1.0.4Updated Oct 26, 2026

Meta Muse (muse.ai) agent chat with its live browser, images, videos with sound and its Library

VerifiedStreamable HTTPWeb executableMedia & DesignAI & ML

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant chat with Meta Muse (muse.ai) agents, including their live browser, images, videos with sound, and Library.

What you can do
  • Chat with Meta Muse (muse.ai) agents through the useapi.net endpoint.
  • Work with the agent's live browser session.
  • Handle images and videos with sound produced or used in the conversation.
  • Access the agent's Library content.
When to use it
Useful when you want an assistant to drive Meta Muse (muse.ai) agents and their live browser, media and Library from a chat client, without running any local software.
Requirements
A remote streamable HTTP endpoint at api.useapi.net. Authentication is required: either an OAuth sign-in supported by clients such as the Claude app or ChatGPT, or an Authorization header carrying a useapi.net API token as a Bearer value. A useapi.net account is implied.
Before you install
The Authorization header carries a useapi.net API token, so treat it as a secret. The server acts on a live browser session and Library content, so assistant actions may change or send data in that account. Requests and media are handled by the third-party useapi.net service.

Installation

In SourceWeft

  1. Open Meta Muse MCP Server by useapi.net (third-party) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/net.useapi%2Fmuse/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "meta-muse-by-useapi-net-third-party": {
      "type": "http",
      "url": "https://api.useapi.net/v1/muse/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

5
  1. v1.0.4LatestOct 26, 2026
  2. v1.0.3Oct 18, 2026
  3. v1.0.2Oct 15, 2026
  4. v1.0.1Oct 15, 2026
  5. v1.0.0Oct 14, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Useapi integrations