Platform

tech.somewherePublished by somewhere.techOfficial publisherv1.0.1Updated Oct 24, 2026

Backend for AI-built apps: database, auth, files, email, AI, payments, deploy, realtime. 170+ tools.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

A remote MCP backend for AI-built apps, giving an assistant tools for database, auth, files, email, AI, payments, deploy and realtime.

What you can do
Manage app data and database resources for AI-built apps, with 170+ tools in total across the platform's services. Handle authentication and user access for those apps. Work with files and send email from within the assistant. Use AI and realtime features, and deploy the app. Take payments through the platform's payment service.
When to use it
Useful when you are building or running an app on this platform and want an assistant to manage its backend directly: data, users, files, email, payments, AI features and deployment, rather than switching between dashboards.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package. OAuth is required, passed as an Authorization header carrying a bearer token: either a developer API key (smt_...) for server-side use or a session token from the provider's auth login command.
Before you install
The Authorization header carries a secret bearer token; keep it out of shared logs and chats. The tools cover payments and deployment, so an assistant may be able to move money or push changes to a live app. Data and operations go to the provider's hosted backend, and write actions should be reviewed before they run.

Installation

In SourceWeft

  1. Open Platform 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/tech.somewhere%2Fplatform/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": {
    "platform": {
      "type": "http",
      "url": "https://mcp.somewhere.tech/mcp"
    }
  }
}

README

This repository has no README.

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

1
  1. v1.0.1LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.