deeptap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPTAP_API_KEY | Yes | API key (dt_live_…), sent as Authorization: Bearer. | |
| DEEPTAP_API_URL | No | Base URL of the DeepTap API (override for self-hosting/staging). | https://deeptap.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountA | Return the current DeepTap account, plan, and limits. Call this first to check the plan and how many domains/links are available before creating resources. Read the |
| list_domainsA | List all DeepTap domains for the account, with their iOS/Android config and AASA/assetlinks URLs. |
| get_domainA | Fetch one domain by id (e.g. 'dom_42'), including its iOS/Android settings and generated file URLs. |
| create_domainA | Create a DeepTap subdomain and configure iOS Universal Links and/or Android App Links. Pass |
| update_domainA | Update a domain's iOS/Android configuration (partial — only the fields you pass change). iOS caches AASA aggressively; existing installs may take up to 24h to pick up changes. |
| verify_domainA | Fetch the domain's generated apple-app-site-association and assetlinks.json and check them against the configured app identifiers (reachable, valid JSON, appID/package match, fingerprints, paths). Run after create_domain/update_domain. Note: this checks what is verifiable server-side; rebuilding the app and on-device checks are still required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a unique purpose: account info, domain verification, listing, retrieval, creation, and updating. No two tools overlap, and the distinction between list/get and create/update is clear.
All tools follow a consistent verb_noun pattern in snake_case (get_account, verify_domain, list_domains, get_domain, create_domain, update_domain). This makes the API predictable and easy to navigate.
With 6 tools, the server covers its domain management purpose without excess. Each tool is necessary and the count is typical for a focused CRUD-style API.
The domain lifecycle is mostly complete with list, get, create, and update, but a delete_domain operation is missing. The verify_domain tool adds value, yet the absence of delete is a minor gap for full resource management.