Interart

app.interartPublished by interart.appOfficial publisherv1.1.1Updated Oct 24, 2026

Create and publish AR designs with video, images and text. Get live links and QR codes.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Interart lets an assistant create and publish augmented-reality designs combining video, images and text, and obtain live links and QR codes.

What you can do
Create AR designs that combine video, images and text, and publish them for viewing. Retrieve live links and QR codes for the published designs. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to help assemble and publish augmented-reality content, such as a design mixing video, images and text, and to get a shareable link or QR code for it.
Requirements
A remote MCP endpoint at mcp.interart.app over streamable HTTP, with OAuth authentication required. No environment variables or headers are declared.
Before you install
Publishing creates content that is publicly reachable through live links and QR codes, so review designs before publishing. Access is tied to an OAuth account, and the manifest does not document what data is sent to the service.

Installation

In SourceWeft

  1. Open Interart 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/app.interart%2Finterart/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": {
    "interart": {
      "type": "http",
      "url": "https://mcp.interart.app/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

3
  1. v1.1.1LatestOct 23, 2026
  2. v1.1.0Oct 23, 2026
  3. v1.0.0Oct 23, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.