CodeQR Typescript MCP Server

Created By
packages8 months ago
Typescript-based MCP server for integrating with the CodeQR API. It enables developers to dynamically access and manage CodeQR tools, short links, and QR code endpoints within their workflows.
Overview

What is the CodeQR TypeScript MCP Server?

The CodeQR TypeScript MCP Server is an open-source server built with TypeScript that integrates seamlessly with the CodeQR API. It allows developers to dynamically access and manage short links, QR codes, analytics, tags, domains, projects, and tracking events directly from any MCP-compatible client.

How to use the CodeQR MCP Server?

  • Launch it with npx or via MCP client config
  • Set your CODEQR_API_KEY environment variable
  • Choose whether to expose all endpoints or use dynamic tools
  • Filter available tools by resource, operation type (read/write), or tags

Key Features of CodeQR MCP Server?

  • Links: create, update, list, delete, bulk operations, and upsert
  • QR Codes: generate, update, list, delete, bulk operations, and upsert
  • Analytics: retrieve performance data for links, domains, and workspaces
  • Tags & Domains: organize and manage resources programmatically
  • Projects: retrieve and list workspace projects
  • Tracking: record leads and sales for short links
  • Dynamic Tools: discover, explore, and invoke endpoints at runtime

Use Cases of CodeQR MCP Server?

  1. Automating short link and QR code creation inside workflows
  2. Retrieving analytics to monitor marketing and campaign performance
  3. Managing multiple domains, tags, and projects from code or AI agents
  4. Extending AI-driven workflows (Claude, Cursor, OpenAI Agents, etc.) with CodeQR tools

FAQ from CodeQR MCP Server?

What do I need to set up the CodeQR MCP Server? A valid CodeQR API Key from your CodeQR account.

Can it be integrated with multiple MCP clients? Yes. It supports Claude, Cursor, OpenAI Agents, and other MCP clients.

Does it support dynamic endpoint discovery? Yes. Using --tools=dynamic, you can discover and invoke any API endpoint dynamically.

Can I filter endpoints? Yes. Filters can be applied by tool, resource, operation type, or tags.

Server Config

{
  "mcpServers": {
    "codeqr_ts_api": {
      "command": "npx",
      "args": [
        "-y",
        "@codeqr/ts-mcp",
        "--client=claude",
        "--tools=dynamic"
      ],
      "env": {
        "CODEQR_API_KEY": "My API Key"
      }
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
packages
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago