Frijolito

io.github.slyaidevelopPublished by GitHub account slyaidevelopv1.0.0Updated Oct 25, 2026

Verify Frijolito receipts, read your Frijolito context, and file or follow requests with the team.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote Frijolito server that lets an assistant verify Frijolito receipts, read your Frijolito context, and file or follow requests with the team.

What you can do
Verify Frijolito receipts and check their validity through the server's verification tools. Read your Frijolito context so the assistant can work from your account's information. File requests with the team and follow their progress. Access is tied to your Frijolito account through OAuth sign-in.
When to use it
Useful when you work with Frijolito and want an assistant to check receipts, pull your account context, or submit and track team requests without switching apps.
Requirements
A remote server reached at the Frijolito endpoint over streamable HTTP. OAuth authentication is required, so you need a Frijolito account and must complete the sign-in flow. No environment variables or headers are declared.
Before you install
Sign-in grants the assistant access to your Frijolito account context, so review the OAuth scopes before authorizing. Filing requests sends data to your team and may create or change records in Frijolito; confirm before submitting. Receipt and context data is shared with the remote service.

Installation

In SourceWeft

  1. Open Frijolito in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.slyaidevelop%2Ffrijolito/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "frijolito": {
      "type": "http",
      "url": "https://frijolito.app/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 25, 2026

Score

75% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.