Society Abstract MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port for the MCP server (default: 3101) | 3101 |
| TESTNET | Yes | "true" for testnet, "false" for mainnet | |
| ABSTRACT_RPC_URL | Yes | Abstract network RPC URL | |
| MCP_DISABLE_PINGS | No | "true" to disable ping messages | |
| ABSTRACT_PRIVATE_KEY | Yes | EOA private key that pays gas fees |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ab_deploy_token_erc20A | Deploy an ERC-20 BasicToken to the Abstract network. PARAMETERS
FLOW
SECURITY / LIMITATIONS
|
| ab_get_balanceA | Fetch the current on-chain balance for a wallet. CAPABILITIES • Native ETH balance (default) • ERC-20 balance via tokenAddress OR well-known tokenSymbol (lookup table) • ENS name resolution for the target address EXAMPLES
RETURNS • Human-readable string (e.g. "12.3456") SECURITY • Read-only operation, no gas spent; safe to run frequently. |
| ab_transfer_tokenA | Transfer value from the caller’s wallet to another address. FUNCTIONALITY • Native ETH transfer (simple payment) • ERC-20 transfer (requires tokenAddress or known tokenSymbol) • ENS resolution for recipient VALIDATION & LOGGING • Ensures wallet signer configured, token decimals fetched automatically • Logs tx hash on success so the agent can create explorer links COMMON USE-CASES • Payout scripted rewards • Move workshop faucet tokens to students • Automation flows needing programmatic payment |
| ab_agw_create_walletA | Deploy a new Abstract Global Wallet (smart-contract account) for a given signer. The tool wraps @abstract-foundation/agw-client’s Returns both the smart-account address and the deployment tx hash ( |
| ab_generate_walletA | Generate a brand-new Externally Owned Account (EOA). RETURNS • privateKey – 0x-prefixed 32-byte hex string • address – checksummed Ethereum/Abstract address COMMON USES • Let agents spin up their own keypairs before funding or deploying smart-accounts. SECURITY • The private key is returned in plaintext. Ensure the caller stores it securely and never logs it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: creating a smart-contract wallet, deploying an ERC-20 token, generating an EOA wallet, fetching balances, and transferring tokens. There is no overlap in functionality, and the descriptions clearly differentiate their roles in the blockchain interaction workflow.
All tools follow a consistent 'ab_' prefix with descriptive verb_noun patterns (e.g., create_wallet, deploy_token, generate_wallet, get_balance, transfer_token). This uniformity makes the toolset predictable and easy to navigate, with no deviations in naming conventions.
With 5 tools, the set is well-scoped for interacting with the Abstract network, covering key operations like wallet management, token deployment, balance queries, and transfers. Each tool serves a distinct and necessary function without being overly sparse or bloated.
The toolset provides comprehensive coverage for core blockchain interactions, including creation, deployment, querying, and transferring. A minor gap exists in lacking update or delete operations for deployed contracts or wallets, but agents can work around this as these are less common in typical workflows.