
TDA Shared Bridge
io.github.targeteddesignagency-blipPublished by GitHub account targeteddesignagency-blipv1.0.0Updated Oct 24, 2026
Agent coordination, email pipeline, lead verification, and campaign operations. 38 tools.
Overview
TDA Shared Bridge is a local desktop MCP server offering 38 tools for agent coordination, email pipelines, lead verification and campaign operations.
- What you can do
- Coordinate agents and shared work through the bridge's coordination tools, as described in the registry entry. Run an email pipeline and campaign operations, per the description. Verify leads as part of campaign workflows. The registry lists 38 tools in total, but no tool names, parameters or documentation are provided, so the exact actions each tool performs cannot be confirmed.
- When to use it
- Consider it when you want an assistant to help coordinate multiple agents or run email and lead-verification campaign work from a local desktop setup. Because no tool list or README is available, only add it if you already know the provider and its workflows.
- Requirements
- Runs as a local process on the user's machine over stdio and is desktop only; it is not available as a web executable. No packages, environment variables, headers or authentication are declared, so any runtime or credential needs are undocumented.
Installation
In SourceWeft
- Open TDA Shared Bridge in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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.