A shared home for community-built connectors that bring apps and services into Umbod. Find a connector, contribute one for a service you use, or improve an existing integration.
Connectors use the Umbod Python SDK, with each operation exposed as a separate tool so users control permissions in Umbod. Contributions for new services are welcome—see CONTRIBUTING.md.
LinkedIn and Nemlig are the first connectors in the collection. Each connector has its own setup instructions and scope.
| Connector | Tools | Functionality |
|---|---|---|
| 20 | Profiles, visits/viewers, feed, posts, comments/reactions, connections/invitations, people/jobs search, messaging, notifications | |
| Nemlig | 7 | Account check, product search/details, basket viewing/quantity changes, order history/details |
The initial connectors have mocked provider request tests and real local MCP stdio discovery tests. Live provider compatibility is not yet verified. Check each connector's documentation for supported operations, authentication requirements, and limitations. Coverage and source revisions.
Requires uv and Git. uv installs Python 3.14 and the connector dependencies in an isolated tool environment; it does not modify Umbod's bundled runtime.
uv tool install --python 3.14 \
'git+https://github.com/computerlovetech/umbod-community-connectors.git@v0.1.0'
uv tool dir --binIn Umbod Desktop, choose Add connector → Local process (stdio):
| Field | Value |
|---|---|
| Name | A name for your connection |
| Executable | Absolute path to umbod-community inside the bin directory printed above |
| Arguments (one per line) | The connector ID from its setup instructions |
| Authentication: environment variable name | UMBOD_CONNECTOR_CONFIG |
| Authentication: secret value | Configuration JSON described in the connector's setup instructions |
Save the connector, use its status tool to check the connection, and enable the tools you want. Umbod stores the secret environment value in Keychain and passes it to the local connector process. Configuration is never part of the model's tool arguments. Authentication is connector-specific; follow its setup instructions. The initial connectors do not provide automatic browser sign-in.
Write tools are present alongside read tools. There is no blanket read-only switch or generic HTTP tool. Use Umbod's per-tool permissions; enabling a write tool authorizes that capability within Umbod's policy. Tool annotations describe side effects but are not authorization checks. Each connector documents which operations have side effects.
Each account should be a separate connector entry with its own configuration. No connector credentials, account content, or tokens are written by this package to files. Session behavior is documented per connector. Provider requests are not automatically retried, avoiding duplicate writes after uncertain failures.
Connectors are also published in the standard umbod.connectors entry-point group. The plugin objects use the public SDK Connector interface, configuration models, configuration checks, and tool decorators. An SDK-compatible Umbod backend can discover the installed package through these entry points. For Enterprise, follow Umbod's plugin bundle deployment guide; installing this tool environment does not install a plugin in an Enterprise backend.
Desktop uses a small stdio launcher over the same SDK tool definitions. It requires no Desktop changes, catalog support, or custom plugin loader.
The current PyPI package named umbod does not provide this SDK release. We therefore pin the SDK to a public Umbod commit in pyproject.toml, and commit uv.lock. See architecture for the compatibility contract.
git clone https://github.com/computerlovetech/umbod-community-connectors.git
cd umbod-community-connectors
uv sync --locked
uv run pytest
uv run ruff check .
uv run ruff format --check .
uv run umbod connectors check
uv buildTests use synthetic credentials and deny live HTTP. See CONTRIBUTING.md to add or update a connector.
Shout-out to Mark Ruvald (@eisbaw) for the inspiration and protocol research in linkedin-rs and nemlig_cli. The initial LinkedIn and Nemlig connectors are independent Python implementations informed by his CLIs. Thank you, Mark!
Code in this repository is MIT licensed. No upstream source files are bundled. Attribution and inspected source revisions are recorded in ACKNOWLEDGEMENTS.md.