TeleQuick Platform

dev.telequickPublished by telequick.devOfficial publisherv0.1.0Updated Oct 24, 2026

Tenant-scoped control plane over the TeleQuick platform's full API surface

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A tenant-scoped remote control plane that lets an assistant call the TeleQuick platform's full API surface.

What you can do
TeleQuick Platform is a remote MCP server that exposes a tenant-scoped control plane over the TeleQuick platform's full API surface. The manifest lists no individual tools, so the specific operations available are not documented here. Access is scoped to a single tenant and authenticated with an MCP access key.
When to use it
Consider it when an assistant needs to work with the TeleQuick platform through its API from a tenant-scoped connection, rather than through separate integrations. Because the tool list is not published, check the provider's documentation first to confirm it covers the operations you need.
Requirements
A remote streamable HTTP endpoint at portal.telequick.dev; no local package or runtime is needed. Authentication is required via OAuth and an Authorization header carrying a bearer MCP access key, which is minted in the console under Admin, API keys, MCP access keys. Network access to the endpoint is required.
Before you install
The server requires a secret MCP access key supplied in the Authorization header; treat it as a credential and keep it out of logs and shared configuration. The manifest does not list the tools, so the scope of what the assistant can read or change in the tenant is unclear; review the provider's documentation before granting access.

Installation

In SourceWeft

  1. Open TeleQuick 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/dev.telequick%2Fportal/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": {
    "telequick-platform": {
      "type": "http",
      "url": "https://portal.telequick.dev/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

1
  1. v0.1.0LatestSep 16, 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.