Connections

io.github.LunarwerxPublished by GitHub account Lunarwerxv2.253.0Updated Oct 24, 2026

AWS, GitHub and connected services from your agent, no keys to paste, plus local shell and browser.

The publisher's own server: Connections

Overview

AI-generated overview

A local MCP server that gives an assistant access to AWS, GitHub and connected services without pasted keys, plus local shell and browser control.

What you can do
Connect the assistant to AWS, GitHub and other linked services without pasting credentials into the chat session, according to the description. Provide local shell access so the assistant can run commands on the machine. Provide local browser control for page work. Scope the session to a chosen workspace folder.
When to use it
Worth considering when you want an assistant to work across cloud and code-hosting accounts plus local shell and browser tasks from one local server, and you prefer not to paste API keys into the conversation.
Requirements
Runs as a local process on the user's machine, installed from the npm package connections-mcp over stdio. Desktop client only; not executable in a web context. Optionally set the CONNECTIONS_WORKSPACE environment variable to an absolute folder path; it defaults to the client's working directory. Accounts for the connected services are implied by the description.
Before you install
The server gives the assistant local shell and browser control, so commands and page actions can change or delete data on your machine. It reaches AWS, GitHub and other connected services, which may allow writes and spending in those accounts. The description says no keys are pasted, but the connection mechanism and where credentials are stored are not documented here; review before use. The workspace variable sets which folder the session operates on.

Installation

In SourceWeft

  1. Open Connections in the dashboard and add it to a workspace.
  2. 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.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

4
  1. v2.253.0LatestOct 18, 2026
  2. v2.240.0Oct 12, 2026
  3. v2.231.0Oct 10, 2026
  4. v2.191.4Sep 29, 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.

Other Connections integrations