HTTP Request Sender: Single or Bulk API Calls from CSV or Sheet

io.github.Nero-EnginePublished by GitHub account Nero-Enginev0.1.1Updated Oct 24, 2026

Send one HTTP request, or one per row of a dataset, CSV or Google Sheet, and get the response back

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

Apify-hosted remote MCP server that lets an assistant send a single HTTP request or one request per row of a dataset, CSV or Google Sheet and return the…

What you can do
  • Send a single HTTP request and get the response back.
  • Send one HTTP request per row of a dataset, CSV file or Google Sheet and collect the responses.
  • Use it to turn tabular data into bulk API calls without writing a script.
When to use it
Useful when you need to fire off one API call, or repeat the same call across many rows of a spreadsheet or dataset, and want the results returned to the assistant.
Requirements
Remote MCP endpoint at mcp.apify.com over streamable HTTP. Requires an Apify account and an Apify API token sent as a Bearer token in the Authorization header (OAuth also declared). Network access to the endpoint and to the target APIs.
Before you install
The Authorization header carries your Apify API token, a secret. Runs are billed per event to your Apify account, so bulk requests over large datasets can cost money. Requests are sent to third-party endpoints you specify, and the server may write to or change data on those endpoints.

Installation

In SourceWeft

  1. Open HTTP Request Sender: Single or Bulk API Calls from CSV or Sheet 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.Nero-Engine%2Fdataset-to-rest-api/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": {
    "http-request-sender-single-or-bulk-api-c": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=nerolabs/dataset-to-rest-api"
    }
  }
}

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

2
  1. v0.1.1LatestOct 2, 2026
  2. v0.1.0Sep 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 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.

  • 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.