Feeefapp Mcp

ai.smitheryPublished by smithery.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Enable AI assistants to interact seamlessly with Feeef e-commerce stores, products, and orders usi…

The publisher's own server: 222wcnm Bilistalkermcp

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint that lets an AI assistant work with Feeef e-commerce stores, products and orders.

What you can do
Work with Feeef e-commerce stores, products and orders through the server's tools, which are not itemized in the available listing. The registry description frames the server as a way for assistants to interact with Feeef store data. No tool list, instructions or README were supplied, so the exact operations and their scope cannot be confirmed from this entry.
When to use it
Consider it when an assistant needs to reach a Feeef e-commerce store to work with its products or orders, and you are comfortable connecting through a hosted Smithery endpoint.
Requirements
A remote MCP connection to the Smithery-hosted endpoint. An Authorization header carrying a Bearer token for Smithery authentication is declared; no environment variables or packages are listed.
Before you install
The server requires a Bearer token in the Authorization header, so treat that credential as a secret. The description mentions stores, products and orders, which suggests access to business data and possibly write operations, but the available listing does not confirm which actions change data. Requests go to a third-party hosted endpoint.

Installation

In SourceWeft

  1. Open Feeefapp Mcp in the dashboard and add it to a workspace.
  2. 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/ai.smithery%2Ffeeefapp-mcp/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.

{
  "mcpServers": {
    "feeefapp": {
      "type": "http",
      "url": "https://server.smithery.ai/@feeefapp/mcp/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 listedRequired15 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Smithery integrations