Ramp Connector for Muse
Read-only view of corporate spend: transactions, cards and limits, users, departments.
- What
- Read-only view of corporate spend: transactions, cards and limits, users, departments.
- Cost
- Free
- Needs
- Ramp API client id and secret (dashboard > Settings > Developer), kept in your Muse's secure vault (never paste secrets here). Read-only by design: it cannot spend, issue cards, or pay bills — request read-only scopes only. Reading needs no confirmation. Ramp's platform is free for businesses.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that inspects a Ramp corporate-spend account without any ability to move money: list and retrieve transactions, list cards with their spending restrictions, list users, and list departments. Read-only by design — it cannot issue cards, set limits, pay bills, or reimburse, because no write code path exists. Uses OAuth 2.0 client credentials with read-only scopes. Draft: written from Ramp's public developer docs, not yet live-tested end-to-end — this listing's unverified status reflects that. No secrets in the repo.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Install
Prerequisites: Ramp API client id and secret (dashboard > Settings > Developer), kept in your Muse's secure vault (never paste secrets here). Read-only by design: it cannot spend, issue cards, or pay bills — request read-only scopes only. Reading needs no confirmation. Ramp's platform is free for businesses. No GitHub account needed unless listed here. Install "Ramp Connector for Muse" for me. A Muse agent skill with read-only access to corporate spend: transactions, cards and limits, users, departments. Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/ramp 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "ramp". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my Ramp API credentials in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.