NOIZDocs
DashboardGet started

Connect an app

Any MCP app

Connect any app that takes a remote MCP server with OAuth.

Any app that takes a remote MCP server over Streamable HTTP and supports OAuth can connect. Noiz publishes the standard metadata, so the server URL is all an app needs to find the sign-in.

Connect

  1. Add the server URL

    Wherever your app takes a remote MCP server, give it:

    Server URL
    https://mcp.noiz.bio/mcp

    Choose OAuth if the app asks how to authenticate. It finds the rest on its own and opens noiz to sign in.

  2. Choose what the app may do

    The app opens noiz's consent page on mcp.noiz.bio. It names the app and lists three permissions. Reading your page is always on; check the others you want:

    • See your page: your name, bio, location and links
    • See your page's views and clicks
    • Change your links, name, bio and location

    Then click Continue.

  3. Sign in on noiz

    You sign in on app.noiz.bio, the same way as for your dashboard. If your account uses two-factor authentication, noiz asks for your code every time you connect an app, even on a device it remembers.

  4. Confirm the account

    Noiz asks Connect as @yourname? Click Connect and you are back in the app, connected. It never saw your password.

  5. Use it

    Ask the app about your page.

    Try:

    • “What links are on my noiz page right now?”
    • “Which link got the most clicks in the last 30 days?”
    • “Add my new video as a link and move it to the top.”
    • “Rewrite my bio in two short sentences.”

Disconnect

To disconnect, open Settings, Security, Connected apps in your dashboard and click Disconnect. That ends the app's access at once. Removing noiz inside the app only makes the app forget its key.

For client developers

WhatValue
TransportStreamable HTTP, stateless
Endpointhttps://mcp.noiz.bio/mcp
Protected resource metadatahttps://mcp.noiz.bio/.well-known/oauth-protected-resource/mcp
Authorization server metadatahttps://mcp.noiz.bio/.well-known/oauth-authorization-server
Client identificationClient ID metadata documents (CIMD), or dynamic client registration
PKCERequired, S256
Resource indicatorhttps://mcp.noiz.bio/mcp

An unauthenticated request to the endpoint answers 401 with a WWW-Authenticate header that points to the protected resource metadata. The full sequence is under Sign-in and consent.